[KPhotoAlbum] Git migration

Andreas Neustifter andreas.neustifter at gmail.com
Tue Oct 12 07:09:38 BST 2010

Hi all!

On 11 October 2010 18:03, Jan Kundrát <jkt at gentoo.org> wrote:

> Andreas Neustifter wrote:
>> I have maintained a GIT Mirror of the SVN repository at github for a
>> while but the setup was not working properly and there were some
>> unrelated commits, so I recreated the mirror from scratch and now at
>> http://github.com/astifter/KPhotoAlbum-SVN-Mirror
>> there is a GIT mirror of the official SVN repository.
> last time I checked there were some suggestions against using git-svn for
> publicly available repositories, but I do not recall specific details
> anymore, and can't think of any at the moment.

In my experience it really sucks if Git and SVN originated commits clash.
When using it purely as mirror, checking in everything in SVN, this
mirroring works just fine.

> I have plenty of other stuff to do, and given that you've already done
> "something similar", you're the usual suspect for the #2 item.

You gotta love track records :-)

> All in all, I do not care that much -- I use my own git-svn clone and work
> happily inside that.

Thats my attitude right now, SVN is perfectly fine for repository hosting
but its terrible for local copies, so having a Git mirror of the SVN stuff
is (IMHO) a quite okay solution.

I remember that Jesper was not in favor of the migration process, mainly
> because of the "if it ain't broke, don't fix it" attitude.

And he is pretty much spot on with that. And with the number of contributors
to KPA that do not have direct commit access to SVN the Git mirror enables
them to have proper working copies, then they send in patches and get the
result via SVN and the Git mirror back into their repository.

> Unless he gets persuaded, the switch won't happen, and I guess that the
> biggest selling point would be "well, most of KDE is switching right now, or
> will switch pretty soon, and following all other projects would lower the
> barrier to entry for newcomers", IMHO.

On the other hand letting other projects build up the expertise and teaching
the users and then making the jump late also has its merrits.

> Just my two cents.

Thanks for taking the time to comment on this, I guess for now there is no
immediate pressure to make the transition.

Besides that maintaining a Git repo with patches coming in can be a little
overwhelming at first (its not as straight forward as SVN) and I would not
like Jesper to have less time for KPA because of that :-)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kphotoalbum/attachments/20101012/457d6bae/attachment.htm>

More information about the Kphotoalbum mailing list