|
From: Florian K. <br...@ac...> - 2011-03-03 00:33:52
|
On 03/02/2011 06:45 AM, Christian Borntraeger wrote: > > I second Barts opinion. Git (or mercurial) would allow private branches > and Julian doesnt have to do anything to make that work (e.g. setting up > the svn users). svn allows restricting accesses to branches and it's not all that complex: http://svnbook.red-bean.com/en/1.5/svn-book.html#svn.serverconfig.pathbasedauthz It's probably less work doing this than setting up and synching an additional repository. Although I wouldn't mind seeing valgrind move to git altogether. > This would help in several cases: It would also help with the s390 port maintenance. Most of my patches will be in VEX and I wouldn't be able to check them into mainline. AFAICT Julian is the only one who can make changes there. Unless that changes, the current setup requires me to maintain a patch queue for VEX changes which is less than ideal because it's clumsy and error prone. Not to mention synching those patches with collaborators. That is what I currently do and it isn't very attractive. Florian |