[Kde-scm-interest] initial port of scripty to git is ready

[Thomas Zander]

On Thursday 21. May 2009 15.16.05 Ian Monroe wrote:
> > 3. There is no 'git push' back into the main repository from scripty's
> > clone

That should be added then; ;)
some algorithm along the lines of
  while (!git push) {
    if (!git pull --rebase) { # sorry, not working out...
     git reset --hard origin/master;
     quit;
    }
  }

> So that we're on the same page... scripty still needs to work with
> i18n in SVN. I was a little concerned when you said its a "git port"
> when its really more of a "git feature addition." I guess I should've
> dented immediately. :)
>
> The idea is that for Amarok or Plasma to switch to git tomorrow, i18n
> needs to stay in SVN. (Possibly i18n could stay in SVN forever, they
> have a very different way of doing things and switching to git should
> be up to them.)

It would be great to have the functionality in place for amarok/plasma to go 
git.
I'm a bit confused about the conclusion we don't want to have i18n in git. 
There are loads of solutions to migrate, including having nice GUI tools so 
the user never need to see a command line.
Keeping svn seems a bit odd to me; an opt-out solution. Not solving the 
problem but avoiding it with the side effect of having to keep an svn server 
up and running :/

So, like Matt I was under the impression we wanted to port script to 
basically do exactly what it did before, but now using git.
-- 
Thomas Zander
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20090521/acaa9e68/attachment.sig