Oops, I seemed to have been dropped from CC- thus the long delay in replying. On 17:47 Mon 30 Mar 2009, Peter Poeml wrote:
On Wed, Mar 25, 2009 at 01:38:42PM -0700, Brandon Philips wrote:
Any thoughts on why we don't move to git? If a community member wanted to interact it seems like giving them SVN access would be a bottle neck.
Just a thought.
How would that work, or avoid human bottlenecks?
The human bottle neck was getting me commit rights- the code was already written. Since git is distributed I could have made my patch commit to a private repo and you could have pushed my change into the "mainline" repo without giving me commit rights to the mainline repo. It would have saved the longish process of getting me commit rights.
I don't really understand how a switch to git (which would cost us quite some effort I assume) would enable you to get changes into mainline easier.
Looking at it longer term that means you can have community members contributing code to the buildservice without having to copy around patches or hand out commit rights. I can't imagine moving the buildservice from SVN to git would be a lot of effort. I am sure most of the developers are already familiar since a lot of the Ruby on Rails community is uses git. Cheers, Brandon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org