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

Re: COMMITTED and subdir recursion

From: Andreas J. Koenig <andreas.koenig_at_anima.de>
Date: 2003-01-20 11:52:45 CET

 On Mon, 20 Jan 2003 11:05:11 +0100, Rafael Garcia-Suarez rgarciasuarez@free.fr said:

   Here is a small test that demonstrates the behavior :
   (I've only 0.16.0 here, but I don't think this has changed recently)

       $ svnadmin create repos
       $ svn co file:///home/rafael/tmp/repos wc
       Checked out revision 0.
       $ cd wc
       $ touch foo; svn add foo; svn ci -m 'add foo'
       A foo
       Adding foo
       Transmitting file data .
       Committed revision 1.
       [rafael@rafael wc]$ svn log -r COMMITTED .
       No commit for revision 0.

Ah, thanks Rafael, now I understand. We have the lagging directoy
problem once again.

Let me point out that especially the svn manpage is misleading. When I
leave the . off as in:

  % svn log -r COMMITTED
  No commit for revision 0.

this seems to be a contradiction to what I read in the manpage:

       log [url] [file|dir] [New-Repository-Entry] [--targets
       file] [--username name] [--password pass]
       [--no-auth-cache] [--strict] [--xml] [-rqv]
              Show log messages (and affected entities) for com#
              mits in which any of the entities in question
              changed. If none were specified, then recursive
              inclusion is the default. [...]

Reading the last sentence, one could conceivably expect that 'svn log
-r COMMITTED' should find out that the last commit was rev 1. Actually
I did believe it would.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:02:18 2006

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.