[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: log <wc> vs log <url>

From: Rob Oxspring <roxspring_at_imapmail.org>
Date: 2003-10-16 17:29:23 CEST

----- Original Message -----
From: "Julian Foad" <julianfoad@btopenworld.com>
To: "Rob Oxspring" <roxspring@imapmail.org>
Cc: <dev@subversion.tigris.org>
Sent: Thursday, October 16, 2003 3:05 PM
Subject: Re: log <wc> vs log <url>

> Rob Oxspring wrote:
> > Is there a rationale behind different results for running "svn log"
> > a working copy verses the "equivelant" url? I've long been happily
> > "svn log ." to find what changes have happened *within* the current
> > directory and have just twigged that instead of that, it's quite
> > showing the changes that happened *to* the current directory.
> Both forms of "log" are inherently recursive. There is no non-recursive
> The only difference I can think of is that "svn log URL" logs up to the
> revision if you don't specify a revision, and "svn log WC-PATH" logs up to
> BASE revision of the WC-PATH. Ah, perhaps that's what is catching you: if
> have modified stuff inside the WC-PATH but have not done an "svn update"
> WC-PATH itself, then the log up to the BASE revision of WC-PATH will not
> showing the changes inside the directory because they happened more
> than BASE.

Thanks Julian - you've hit the nail on the head. I hadn't done a full
update for a little while and so, for the directory at least, BASE and HEAD
had drifted enough to confuse me. Obviously I'd agree with Philip that
wc@BASE vs url@HEAD should be made clear in the --help text but I'll leave
it to you guys to figure if/how/where to document it.

Thanks all, keep up the good work,


> Try "svn log -rHEAD:1 ."
> - Julian

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 16 17:30:18 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.