On 3/23/07, Steve Bakke <firstname.lastname@example.org> wrote:
> Would it be possible to set a property on the specific revision of a file
> which would indicate which tag the revision is included in?
> On 3/23/07 4:33 PM, "Les Mikesell" <email@example.com> wrote:
> > Jeff Smith wrote:
> >> On Friday 16 March 2007 16:45, Les Mikesell wrote:
> >>> The point is more that you can't look backwards from the trunk copy
> >>> (or maybe some branch) and see at what point the tag was applied.
> >> In either VCS, don't you have to know the name of the tag before you
> >> can look for it? My point is if you know the tag is named "tag/tag1",
> >> you don't have to look in "trunk" for that tag. The name already
> >> tells where it is. Then you have only to look there to see where it
> >> came from. I don't see any ability that is lost.
> > There is no problem getting an exact copy of the tagged version back and
> > from the tagged version you can see it's history. The problem is
> > knowing how a file in that version relates to anything else. Looking at
> > a file of the same name in the trunk/HEAD you can't tell at what point
> > the tag was applied or even if the file had been deleted and recreated
> > since then and no longer shares any history. Likewise from the tag, you
> > can't follow the 'future' revisions that may or may not exist in the
> > trunk or other branches.
Not really, as creating (or updating) that property creates a new
revision of the file in question. Once a revision is created, it
cannot be changed, so you can't go back after the fact an update
properties. (revision properties, or rev-props are different, but
they are per-revision, not per file.)
Getting the branch/tag 'meta-data' about a file is much harder in
subversion than CVS, and I don't see any easy way to 'fix' it. I have
not seen any tools that really help here, I think that most people
have just learned to not try to get that information from subversion.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Mar 23 23:48:24 2007