Hi Andreas,
On 18 May 2015 at 19:07, Andreas Stieger <andreas.stieger_at_gmx.de> wrote:
> Hello,
>
> On 18/05/15 15:44, Johan Corveleyn wrote:
>> On Mon, May 18, 2015 at 2:59 PM, Nicolai Scheer
>> <nicolai.scheer_at_gmail.com> wrote:
>>> [...]
>>> Currently, I'm trying to solve a seemingly simple task, that is, answer the
>>> question:
>>> "what's new in the release 1.0.1?".
>>> [...]
>> In our build system we generate the list of revision numbers that are
>> in 1.0.1 but not in 1.0.0 by asking svn for the "revisions that are
>> eligible for merging from 1.0.1 to 1.0.0" (i.e. anything that's in
>> 1.0.1 that can sensibly be merged into 1.0.0). I.e.:
>>
>> svn mergeinfo --show-revs=eligible $URL/1.0.1 $URL/1.0.0
>
> Or... extract the copy sources of the tags:
>
> $ svn log ^/subversion/tags/1.8.12 -r1:HEAD -l1 --stop-on-copy -v
> ------------------------------------------------------------------------
> r1667497 | stsp | 2015-03-18 12:08:02 +0100 (Wed, 18 Mar 2015) | 1 line
> Changed paths:
> A /subversion/tags/1.8.12 (from /subversion/branches/1.8.x:1667489)
> ^^^^^^^
> M /subversion/tags/1.8.12/subversion/include/svn_version.h
>
> Tagging release 1.8.12
> ------------------------------------------------------------------------
> $ svn log ^/subversion/tags/1.8.13 -r1:HEAD -l1 --stop-on-copy -v
> ------------------------------------------------------------------------
> r1667548 | stsp | 2015-03-18 14:36:18 +0100 (Wed, 18 Mar 2015) | 1 line
> Changed paths:
> A /subversion/tags/1.8.13 (from /subversion/branches/1.8.x:1667537)
> ^^^^^^^
> M /subversion/tags/1.8.13/subversion/include/svn_version.h
>
> Tagging release 1.8.13
> ------------------------------------------------------------------------
>
> And then examine the logs between these two copy sources:
> $ svn log ^/subversion/branches/1.8.x -r1667489:1667537
> ^^^^^^^ ^^^^^^^
> Or, rather, increment the first by 1 to exclude the revision of the
> previous tag:
> $ svn log ^/subversion/branches/1.8.x -r1667490:1667537
> ^^^^^^^ ^^^^^^^
>
> Add --xml to the above for scripting. I have implemented this in a
> number of private tools that integrated with issue trackers. Add some
> XSLT for web display and reporting. Also when parsing mergeinfo you can
> get some trunk logs augmented with information about what was backported
> where, and tags attached to a log view.
Thanks for your suggestion!
Unfortunately this is not possible (anymore), because we recently had
to restructure our folders and needed to move tags around.
Now --stop-on-copy stops on the "wrong" copy which renders this
approach unusable.
Greetings
Nico
Received on 2015-05-19 15:50:45 CEST