Karl Fogel [mailto:kfogel@newton.ch.collab.net] wrote:
> Perhaps you're thinking: "Yes, but if I ran an 'svn up' from the top
> of the tree, then the working revision obtained from some random file
> in that tree would be the same as the rev of the entire directory
> tree, so I could just use that as a tag rev." Which is true, but only
> because you happen to know that you just ran 'svn up' -- knowing the
> working rev for a file doesn't, inherently, tell you anything about
> other files or dirs around it. It only tells you about that one file,
> and what it tells you is basically the same as what the current $Rev$
> keyword would tell you.
I do understand the limitations, why it is potentially unsafe and I may even
appreciate that it will be tricky to implement, give rise to unanticipated
rebuilds, give headaches for CMs and all that.
It made sense to me and what I would use it for.
I just wanted *one* simple little number that described the whole shebang,
and I wanted svn to put it there, in one of my files. And I wanted the
number to have some meaning, so I could recreate the stuff later. It
wouldn't have mattered if it were the Working Revision, or the Last Changed
Revision of the project directory.
Having said that, I'm really quite content to simply tag and use $URL$. But
others may not be. I don't know. There was a little dark spot in the nice
picture and I just wanted to point it out.
Enough said about that.
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 9 23:02:10 2002