On Fri, Sep 23, 2011 at 1:00 AM, Andreas Krey <a.krey_at_gmx.de> wrote:
> Don't make me rant. The svn user interface (at least the one that
> is ontopic here, namely the 'svn' CLI) is horrible, mostly due to
> the fact that svn only pretends to have branches and doesn't have
> tags at all. (It replaces them by a convoluted history tracking, and
> by forcing each installation to write commit triggers, respectively.)
If you want tags to be immutable, you know how to make them that way.
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.
>> good. If run a development shop building a proprietary trading
>> application for a large financial firm, and a million people have a
>> copy of your repository, that's bad.
> For one, the million people still have the current source in their
> sandboxes which is the most valuable part or the repo, and second,
> nothing keeps the bad guy to run svnsync or 'git svn clone' (which
> half of your devs are likely to use anyway) to get a repo copy.
> '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?
Received on 2011-09-23 22:00:12 CEST