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.
On Sat, 2005-04-30 at 21:11 -0500, Ben Collins-Sussman wrote:
> On Apr 30, 2005, at 8:59 PM, Maarten van der Veen wrote:
>
> > Is there a way I can get the date that a revision number was committed?
>
> $svn propget --revprop -r REV svn:date
>
>
> >
> > I try to parse the "svn log --limit 1" output, but doing this on a
> > directory does not always return the latest revision number of the
> > child
> > files/directories.
>
> That's because your working copy is made of mixed revisions, because
> you haven't run 'svn update' for a long time. Run 'svn status -v', and
> notice the working revision of the current working dir. If it's not
> HEAD, then running 'svn log' with no arguments is equivalent to saying,
> "show me the history of this working directory, starting at the
> revision it's at, and going backwards in time." You won't see
> revisions "newer" than the directory's working revision until you
> update. (Or, unless you run 'svn log' on the URL of the directory.)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun May 1 09:17:29 2005