On May 1, 2005, at 11:19 PM, Maarten van der Veen wrote:
> They do give the same result. What I'm saying is, that svn log or svn
> log --limit 1 does not return the highest revision of his children in
> the first place.
>
> I've read that this is normal and that it is only added to the log list
> after you do a svn update. But when I do one, it is still not in the
> log
> list..
>
No offense, but I still don't believe you.... either that, or we
misunderstand each other somehow. :-)
Can you please show us a transcript? In other words, I want to see an
actual cut-and-paste that demonstrates what you say. Show me how 'svn
log' or 'svn log --limit 1' begins by returning revision N, but that
'svn log some child-object' begins by returning a revision larger than
N.
Or... perhaps you're getting confused about the difference between
"working revision" and "last changed revision"? Just because an
object has a working revision of say, HEAD, doesn't mean it *changed*
in HEAD. And 'svn log' on that object certainly isn't going to show
you the HEAD revision. If you run 'svn status -v', notice that each
object has a last-changed-revision: that's the last revision in which
each object changed. And that's the *first* revision that 'svn log'
will return if you ask for the history of the object. Revisions
greater than that value are of no interest to the log command; they
didn't affect the item in question.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 2 06:31:04 2005