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

Re: svn log --stop-on-copy question

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-09-15 16:12:52 CEST

Ben Collins-Sussman <sussman@collab.net> writes:

> Wolfgang Fritz wrote:
> > Hi,
> > if I run a
> > svn log --stop-on-copy
> > on a directory, it stops on the copy.
> > If I run the same command on a file in that directory, it does not stop.
> > (example below). Is that a bug or a feature? I'm running 1.1.0-rc3.
> This is intentional, I think. The --stop-on-copy switch stops when
> the target is *explicitly* copied, rather than *implicitly* copied
> (because some parent was copied).

First, I'm not really sure that statement is true. Secondly, it's
obvious from looking at Wolfgang's 'svn log' output that file in
question *was* explicitly copied.

   r45 | (no author) | 2004-09-14 15:53:26 +0200 (Tue, 14 Sep 2004) | 1 line
   Changed paths:
      A /project1/branches/branch1 (from /project1/trunk:1)
*** A /project1/branches/branch1/Datei1 (from /project1/trunk/Datei1:8)
      A /project1/branches/branch1/fdflush.c (from /project1/trunk/fdflush.c:5)
      A /project1/branches/branch1/modprobe.c (from /project1/trunk/modprobe.c:4)

That said, I'm having trouble reproducing the problem for myself.
Wolfgang, does the behavior change at all if you specify full URLs for
your 'svn log' targets? And if the code isn't proprietary, could you
post a compressed dumpfile of your repository somewhere so I could
take a look-see? Thanks.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 15 16:15:24 2004

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

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