Re: CVS -> SVN -> Git

Markus Schiltknecht <markusbluegap.ch> writes:
> In CVS as well as in subversion, you can modify a tag
after it has
> been created. 

Oh.  I don't think "atomic" is the right word for
the property that is
missing here, but now I understand what you meant, thank
you.

(Subversion can be configured to disallow modifications to
tags, but
you are correct that by default it allows tags to be
modified.)

> And with branches, it's even worse: each file can have
> it's branchpoint at a different point in time. For good
reasons, this
> is not possible with mtn, hg, git, cdv...  (A converter
from
> subversion to any of those will have to cope with that
somehow, much
> like a when converting from CVS).

Heh, well, we disagree on what is desirable here , but now
I
understand the issue.

Thanks for the explanation,
-Karl

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribecvs2svn.tigris.org
For additional commands, e-mail: dev-helpcvs2svn.tigris.org

Hi,

Karl Fogel wrote:
> Oh.  I don't think "atomic" is the right word
for the property that is
> missing here, but now I understand what you meant,
thank you.

Hm.. what would be a better word?

When thinking about it again, it's a very similar issue to
the branch 
thing: in CVS you can tag together files from different
points in time, 
i.e. given you have three commits, each modifying all three
files, you 
could easily tag together fileA  1.1, fileB  1.2 and
fileC  1.3. This 
creates a 'view' or an 'artificial revision' which never
really existed 
in the repository like that. The very same applies for
branchpoints.

I hope that's a better explaination.

> (Subversion can be configured to disallow modifications
to tags, but
> you are correct that by default it allows tags to be
modified.)

Even then, you can probably tag together files from
different points in 
time, I guess. My point is, that subversion's storage format
is not as 
universal as it might seem. I would even argue that mtn's
(and therefore 
also git's) storage format is more universal, as they are
closer to the 
mental model of branches and tags. But..

> Heh, well, we disagree on what is desirable here , but now
I
> understand the issue.

Well, that's the VCS world. And probably the reason for the
existence of 
a dozen of VCSen. Of which monotone is clearly the leader


Regards

Markus

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribecvs2svn.tigris.org
For additional commands, e-mail: dev-helpcvs2svn.tigris.org