Well, I for one do this a lot with CVS. I start with a tagged
distribution (which might cross through multiple revisions, of course,
as CVS's tag model is weirdly flexible like that), and then I realize
there seems to be some sort of bug in a file I have. Then, I start
asking for diffs between the various later versions seeing what kinds of
things have been changed before I start fixing it. This usually results
in:
cvs status <file>
This tells me what revision I have. Then:
cvs diff -u -r <next revision> <file>
Thanks to CVS's usage of file based versioning, I know what the next
revision to the file is right quick (which is usually the number I'm
most concerned with). Then, I slowly walk forward viewing later and
later revisions, but now using rdiff so I don't need to actually change
my copy or mentally keep track of what has already been changed:
cvs rdiff -u -r <a revision> -r <the next revision> <file>
Oh god... I just thought of what this is going to be like with
Subversion... the "file" I'm dealing with has no real connection with
the later revisions, so I need to walk back the copy path to figure out
where the file came from, then I have to walk forward the revisions on
that path, which involves figuring out what the next version is in the
first place (as it is linearly independent of the last version), and
then... *is literally wincing in pain*.
As Steve might say: "I had not thought of that!" Technically a massive
client could be built that does that work for me, but it wouldn't be
able to understand the "tags" as real tags due to the concept being a
fiction of the people using the repository and not a generally accepted
"this is the way tags work" that has been coded into the version
control.
And what happens when I want a specific subdirectory to be at one tag
revision from another, but still want to do merge operations, and what
happens when... I KNEW this "quick copy" idea was going to get nasty at
some point, I was just hoping you guys would have already figured out
why it was going to work before it started freaking me out.
Sincerely,
Jay Freeman (saurik)
saurik@saurik.com
-----Original Message-----
From: sussman@collab.net [mailto:sussman@collab.net]
Sent: Wednesday, January 16, 2002 8:40 PM
To: David Summers
Cc: dev@subversion.tigris.org
Subject: Re: Question: Rev 914
...
But, now, grasshopper, I throw a question back at you: why do you
care to know what /tags/0.8.0 is a copy of? Is it not enough that it
merely exists?
I mean, when you tag 300 RCS files with CVS, do you care to examine
the exact list of per-file revisions that the tag represents?
Similarly, do you care to see the exact list of node-ids that live
beneath /tags/0.8.0?
...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:56 2006