Matthias Wächter wrote:
> John Calcote schrieb:
>
>> Stuart Celarier wrote:
>>
>>> John, I think you've overlooked some use cases for tags. Here are three
>>> to consider.
>>>
>>
>> I've seen a lot of comments on additional use cases for tags. It
>> seems most of them can be summarized in the following three use cases:
>>
>> 1. Tags as pure symbolic revisions (snapshot in time)
>> 2. Tags as proper subsets of files within a revision (a snapshot in
>> time and space)
>> 3. Tags as subsets of files with mixed revisions (a snapshot of a
>> corrupt work area)
>
>
> Don't forget that you should be able to tag a tag of a tag and end up
> with the same set of files (and revision numbers!) that you had before
> the tag.
>
> In SVN it is annoying that I run "svnversion" and read "300", after
> tagging the directory (and updating to the tag) the same command
> returns "315". If I tag the same directory again after three years,
> "svnversion" returns 4012 or such.
>
> A solution to all that would be an automated "walk back" feature for
> co/up/cp/export/sw/lock/unlock as brainstormed in
"walk back" is what SVN currently does, on the back-end (due to the
cheap copies). As a general rule: ignore revision numbers. They might as
well be randomly generated. Tagging a tag of a tag gets the same files,
always. Due to the flexibility of tags (being able to tag things which
did not previously exist in the repos), "walk backs" would not always
make sense.
I fear that adding such things would create two seperate classes of
tags, which would lead to confusion.
Perhaps svnversion could have a --last-changed (or something) option to
show when the file /contents/ were last modified. (svnversion seems like
a bad place for this, though. Perhaps "svn blame -q"?)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 21 14:41:31 2006