Philip Martin wrote on Sat, Feb 28, 2015 at 18:12:47 +0000:
> Bert Huijben <bert_at_qqmail.nl> writes:
> > I would have expected that the backport script would *only* look at
> > the branch, as that is what would have to be merged once accepted.
> I suppose I could do the trivial merge from trunk and generate a
> mergeinfo change on the branch. That would probably satisfy the
> backport script.
Why are you *guessing* how the script works? If something is not clear,
please ask, so the documentation may be improved.
The bits you speculated about are documented here (this is the old
documentation, before today's patch):
% ./tools/dist/backport.pl --help | me
Both batch modes also perform a basic sanity-check on entries that declare
backport branches (via the "Branch:" header): if a backport branch is used, but
at least one of the revisions enumerated in the entry title had not been merged
from ^/subversion/trunk to the branch root, the hourly bot will turn red and
nightly bot will skip the entry and email its admins. (The nightly bot does
not email the list on failure, since it doesn't use buildbot.)
If there are any other questions about backport.pl, how it works, etc.,
I'd be happy to answer. Fire away.
Received on 2015-02-28 22:52:52 CET