Thanks, that really clears things up. Appreciate your help!
-r
On Tue, 2005-07-12 at 09:54 -0400, Dominic Anello wrote:
<snip>
>
> This is not a bug. When you update your branch, the BASE revision
> becomes the same as HEAD. If the commit that created HEAD doesn't touch
> your branch, then log will not return any data for your command. You're
> basically asking svn "What happened in rBASE on this branch?" The
> answer in this case happens to be: nothing!
>
> You should probably be using the svnversion tool with the -c option.
> This returns the earliest and latest committed revision in a working
> copy.
>
> Example:
> [danello@lynx ~/src/ec/trunk]$ svn up
> At revision 4512.
>
> [danello@lynx ~/src/ec/trunk]$ svn log -r BASE
> ------------------------------------------------------------------------
>
> [danello_at_lynx ~/src/ec/trunk]$ svn log -q -v -r4512 http://lynx/ec-svn
> ------------------------------------------------------------------------
> r4512 | jcozzens | 2005-07-12 09:33:08 -0400 (Tue, 12 Jul 2005)
> Changed paths:
> M /branches/eCommerce/4.8.0.x/4.8.0-4.8.0.1-post-upgrade/SeeBeyond3x/monk_scripts/common/FILE/Collab/crTRNSIRSFileMask.tsc
> ------------------------------------------------------------------------
>
> [danello@lynx ~/src/ec/trunk]$ svnversion -c .
> 2:4497
>
> I this example, svn log of BASE=4512 on trunk returns no data because
> 4512 didn't touch trunk. When I run svnversion, I get 2:4497. 2 is the
> commit revision of the least recently comitted file. 4497 is the commit
> revision of the most recently comitted file.
>
> -Dominic
--
Ramit Hora <ramit@pando.com>
Pando Networks
QA and Release Manager
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 12 17:06:32 2005