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

Re: Obtaining log messages for a diff

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Wed, 20 May 2015 23:57:04 +0000

Nicolai Scheer wrote on Wed, May 20, 2015 at 11:40:49 +0200:
> On 19 May 2015 at 15:51, Mark Phippard <markphip_at_gmail.com> wrote:
> > Assuming you know the revisions tag in 1.0.0 and 1.0.1 can't you just run
> > svn log on branches/1.0.x and ask for all changes between those two
> > revisions?
>
> Yes, that is the straighforward way. Unfortunately we "broke" this,
> when we restructured our repository and had to move a lot of tags.
> For newly created tags this works - but we needed a universal approach.

You can use --stop-on-copy to determine not only the most recent copy,
but also the one before that (and so on), using peg revisions. You'd
just have to invoke svn multiple times iteratively until you hit the
right copy operation.

The history / location segments APIs should be able to answer this
question in one invocation, but I don't think they're exposed by the
cmdline client.
Received on 2015-05-21 01:57:11 CEST

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.