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..
On Sun, 2005-05-01 at 08:34 -0500, Ben Collins-Sussman wrote:
> On May 1, 2005, at 2:15 AM, Maarten van der Veen wrote:
>
> > Actually, this happens right after I do an svn update on the specific
> > directory. I've read a few topics about this subject and I do not see
> > why I get this problem right after a svn update.
> >
>
> Can you be much more specific? Are you saying that if you run 'svn
> up', then the commands
>
> 'svn log'
>
> and
>
> 'svn log --limit 1'
>
>
> ...don't both begin with the exact same revision, namely, the latest
> revision to affect that directory?
>
> If not, show us a transcript with details that demonstrates.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
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:21:58 2005