subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Krey <>
Subject Re: Use of svnserve and Dropbox
Date Sat, 24 Sep 2011 19:19:17 GMT
On Fri, 23 Sep 2011 14:59:40 +0000, Les Mikesell wrote:
> If you want tags to be immutable, you know how to make them that way.

I want them mostly immutable, that is, not accidentally, but with -f
(which is pretty much the way any other VCS is doing it).

As far as I can see there is no way of making subversion do that.

> On the other hand, a path and revision number are always immutable and
> all you really need a tag for is to have a (slightly) more
> human-friendly name - which you are probably going to cut&paste
> whether it is short and friendly or not.

'ipv6' or 'fdpass' aren't really requiring c&p. On the other hand,
switching branches in svn usually requires 'svn info' and then
c&p'ing the path together out of the old path and the replaced
branch/tag name. Heck, you need to do that even for *finding out*
which branches exist.

And 'module-v1.2.4' is not just 'slighly' more human-readable
than 'trunk@21354', the latter explicitly *not* conveying
the relevant information.

> > 'They don't have the repo' is just an illusion.
> But you can control access to the svn repository at the path level and
> you can't svnsync if you don't have read access.  How do you give a
> person or  group access to only a portion of a git repo?

You don't. You don't put everything into a single git repo as you do
with svn, but only what you would branch/tag separately in svn. And
providing repo-wise access control is no problem.


View raw message