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

RE: Determining origin of branch

From: Derek Mahar <DMahar_at_penson.ca>
Date: 2004-03-30 17:50:18 CEST

Here's a reproducible test case of the --stop-on-copy anomaly. Notice
that the first listing lists two revisions back to the branch copy
point, while the second listing lists just one revision back to the
renaming of the ancestor directory a to b.

svnadmin create /home/svn/test
REPOS=https://localhost/subversion/test
mkdir project
mkdir -p project/a/trunk
mkdir -p project/a/branches
svn import -m 1 $REPOS
svn copy -m 2 $REPOS/project/a/trunk $REPOS/project/a/branches/branch1
svn mkdir -m 3 $REPOS/project/a/branches/branch1/new
svn log --verbose --stop-on-copy $REPOS/project/a/branches/branch1
Output:
------------------------------------------------------------------------
r3 | dmahar | 2004-03-30 10:42:29 -0500 (Tue, 30 Mar 2004) | 1 line
Changed paths:
   A /project/a/branches/branch1/new

3
------------------------------------------------------------------------
r2 | dmahar | 2004-03-30 10:42:22 -0500 (Tue, 30 Mar 2004) | 1 line
Changed paths:
   A /project/a/branches/branch1 (from /project/a/trunk:1)

2
------------------------------------------------------------------------
svn rename -m 4 $REPOS/project/a $REPOS/project/b
svn log --verbose --stop-on-copy $REPOS/project/a/branches/branch1
Output:
------------------------------------------------------------------------
r4 | dmahar | 2004-03-30 10:44:56 -0500 (Tue, 30 Mar 2004) | 1 line
Changed paths:
   D /project/a
   A /project/b (from /project/a:3)

4
------------------------------------------------------------------------

-----Original Message-----
From: cmpilato@localhost.localdomain
[mailto:cmpilato@localhost.localdomain] On Behalf Of C. Michael Pilato
Sent: March 29, 2004 9:53 AM
To: Derek Mahar
Cc: Subversion Users
Subject: Re: Determining origin of branch

"Derek Mahar" <DMahar@penson.ca> writes:

> Yes, I agree, this was the expected behaviour (i.e. Subversion is
> behaving correctly), but my point is that "svn log --stop-on-copy"
> does not under all conditions return the branch copy revision as the
> user might expect. If the user has done any other copy operation
> since that user created the branch, --stop-on-copy stops at that copy
> point rather than the branch copy point. Though it is the correct
> result, this is probably not the result that the user expected (or, in

> other words, the result that the user wanted).

Can you provide a recipe for this behavior? The --stop-on-copy option
should only apply when the target of the log operation was the thing
that got copied. In other words, if you do:

   svn copy trunk branches/foo
   ...
   svn copy trunk/junk branches/foo/junk
   ...
   svn log --stop-on-copy branches/foo

Your log output should continue past the copy of the thing *into* your
branch, and stop with the copy that created your branch. If you've
found an instance where this is not happening correctly, please try to
come up with a reproducible recipe, because that is a bug.
NOTICE: This email contains privileged and confidential information and is intended only for the individual to whom it is addressed. If you are not the named addressee, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this transmission by mistake and delete this communication from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.

AVIS: Le présent courriel contient des renseignements de nature privilégiée et confidentielle et n’est destiné qu'à la personne à qui il est adressé. Si vous n’êtes pas le destinataire prévu, vous êtes par les présentes avisés que toute diffusion, distribution ou reproduction de cette communication est strictement interdite.  Si vous avez reçu ce courriel par erreur, veuillez en aviser immédiatement l’expéditeur et le supprimer de votre système. Notez que la transmission de courriel ne peut en aucun cas être considéré comme inviolable ou exempt d’erreur puisque les informations qu’il contient pourraient être interceptés, corrompues, perdues, détruites, arrivées en retard ou incomplètes ou contenir un virus.  

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 30 17:51:05 2004

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