[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn vs. git

From: Stefan Sperling <stsp_at_elego.de>
Date: Tue, 25 Jul 2017 13:21:29 +0200

On Tue, Jul 25, 2017 at 08:48:07AM +0200, Andreas Krey wrote:
> This also means that I can't maintain a patched version of
> svn (or anything in an svn repo) without having commit
> privilege to the source repo

This is obviously true, and a reason for why the Subversion project
itself has a very relaxed commit access policy. Need a branch?
Just show a nice diff to any full committer and they can make it happen:
https://subversion.apache.org/docs/community-guide/roles.html#partial-commit-access

Granted, this is still an extra hoop you might not want to jump through,
in which case using a git mirror simply makes more sense.

And other projects using SVN may be less open about this, of course.
The point is that people don't need to be walled off still stands.
It is a process problem, not a technical one, unless you're working
at Linux kernel scale with a community of thousands across various
organizations, which Subversion was never intended for.
You might remember the page on subversion.tigris.org around the time
git was first created, which asked people to stop suggesting that Linus
should use SVN: https://svn.apache.org/repos/asf/subversion/branches/1.2.x/www/subversion-linus.html
Received on 2017-07-25 13:21:59 CEST

This is an archived mail posted to the Subversion Users mailing list.