On Fri, 26 Sep 2008, Martin Mohring wrote:
Now my own 2 cent: ...
the only pro for git is that our backend storage is pretty close to a git repository. so the code could be adapted to be compatible.
though we would need our own git daemon: 1. to apply the same access control we do in api atm. 2. to trigger the scheduler events. 3. to update the caches in api for metadata e.g.
So you also propose to split off the revision control system of OBS to something known like git? Your proposal to git is, if I understand you correctly, because git does already nearly the same as the current implementation inside OBS, right?
I think git is the best solution and it handles things a lot cleaner than svn. I have come to really dislike svn. SO I think if a RCS is to be used it should be git. It also is fully Open Source GPL. -- Boyd Gerber <gerberb@zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org