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

Re: Display outstanding backported fixes for each release?

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Sat, 15 Dec 2018 10:10:04 +0000

Julian Foad wrote on Fri, Dec 14, 2018 at 22:30:01 +0000:
> Daniel Shahaf wrote:
> > [...] write a script that:
> > 1. Queries the repository for trunk revnums that have been merged to the
> stable branch since the last tag;
> See attached "svn-revs-backported.sh".

I think the script might break when we reach r10⁷ (r10000000) because
"svn mergeinfo"'s output is sorted numerically, but comm(1) expects its
inputs to be sorted according to strcoll(3).

Currently comm(1)'s precondition does hold, but only because all the
revision numbers in "svn mergeinfo"'s output have the same number of
digits. However, as soon as HEAD passes a power of ten, we'll run into
the problem that "r9" is printed before "r10" (because 9 < 10) but
«!(strcoll("r9", "r10") < 0)». (This is the same problem we warned
about in the 1.9 and 1.10 release notes.)
> > 3. Synthesizes a CHANGES-like listing [...]
> That's one reasonable option.
> I do also wonder if we couldn't implement something that more directly
> queries 'svn' and displays the result. That is, start designing and
> implementing some more powerful querying, starting with "changes in
> 1.10.x but not in 1.10.3".

Would that need new RA APIs?
Received on 2018-12-15 11:10:25 CET

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

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