Saulius Grazulis wrote:
>Have it come to your attention that you request a log using _revision number
>only_ -- you obviously can not read a log before you run 'svn log -r 12598'?
This is for use in conjunction with another command such as svn blame.
That's where the "associated path" comes in in this point.
svn blame somefile.c
(read, see revision number you care about)
svn log -rRevnum somefile.c |less
>And if you say 'svn log -r 12598 repo/my/tag', you are likely to get an empty
>mesage since the tag was committed in, say, 12599?
So don't do that. Subversion has tags so you can say: svn log
repo/my/tag, and see the related log message.
So, yes, if you intentionally use the command wrong, the results will
not make sense. :)
This is the entire point of my previous message: A revision number
without an associated path is meaningless. If you give a revision number
and some random path which is not really associated with, you will get
meaningless results. That's the point.
> So what you want is 'svn
>log -r 12598 repo/ | grep my/tag' or something more elaborate (to get the
>whole log message, not just one line).
The whole point of this thread seems increasingly to be "I do not
understand how svn implements tags"
Paths always have revision numbers associated with them. ("node IDs", I
suppose). If you create a Tag in SVN, as currently implemented, all you
are doing is attaching a name to a collection of related nodes at a
particular revision. You can call the tag whatever you want.
>Which demonstrates, taken to the extreme, that _paths are meaningless_, and
>revision numbers _are the only meaningful thing_. Of course, one wants to
>remember names, not numbers -- hence labels come to life.
If you are mis-using SVN to the point where paths become meaningless,
perhaps you should re-read the book ;)
>>"Show me the log at /tags/release-13" has paths cheaply associated with it.
>At which revision? ;)
It's a tag. Why would I care what revision it was comitted to? I just
want to know "Show me release 13", not "Show me a random number which
happened to come up when release 13 was made".
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Feb 27 14:31:31 2006