Re: log for changes between two tags

From: Mark Ryan <m.ryan_at_phion.com>
Date: 2006-07-25 10:35:40 CEST

Reedick, Andrew wrote:

-----Original Message-----
From: David Everly [mailto:deckrider@gmail.com] 

What is the best way to see the svn log for the delta between 
two tags?
    

 

If they have a common ancestry, then you should be able to find the
revisions on the branch they branched from, and do an 'svn log -r X:Y
...'.

     + tag1 (r103)    + tag2 (r205)
    /                /
---+----------------+----> (trunk)
  r100             r200

Use "svn log --stop-on-copy tag1_url" to determine where it branched
from (r100 on trunk).  Repeat for tag2.
Then "svn log -r 100:200 trunk_url"


*****

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. AL621


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

  

We use a slightly modified approach all the time for getting the changes between two tags and establishing which modules need to be rebuilt after a new tag is created. (Fully  automated naturally - but don't tell the boss as he thinks I work for a living ;-)   ...!!)

However, you need to be careful doing it as documented above as the 'log -r x:y' reports all log entries inclusive, ie. including the first revision (r100 in the previous example). This (to me!) is not actually the delta **between** two tags.

A good example is to create two tags from the same revision and then go through the same exercise, eg. Using the above example "svn log -r 100:100" still returns a log entry eventhough the tags are actually from the same revision - strictly speaking the delta between two identical tags should be null!

For establishing the changes in tag2 since tag1 (which is what I am interested in when performing a rebuild or producing release notes), I establish the lower 'copy from' revision and simply increment this lower revision by one (which of course means you then need to check that "revision++" actually exists and is not higher than the other revision!).

It's not a pretty solution - so if anyone has a better method then please let me know..!!

Cheers

Mark.

 

_______________________________________________________________


This information is confidential and intended solely for the use of the named addressee(s). If you are not the named addressee, any disclosure, copying, distribution or retention of this e-mail is prohibited, may be unlawful and violating attorney/client privilege. If you are not the intended recipient, please inform us immediately and refrain from taking any other action in reliance to this e-mail.

--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org For additional commands, e-mail: users-help@subversion.tigris.org Received on Tue Jul 25 10:33:34 2006