GNU bug report logs - #34776
27.0.50; Some questions about choose-completion-string-functions

Previous Next

Full log

Message #64 received at 34776 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andreas Schwab <schwab <at> suse.de>
Cc: eric <at> ericabrahamsen.net, 34776 <at> debbugs.gnu.org, npostavs <at> gmail.com
Subject: Re: bug#34776: Acknowledgement (27.0.50;
 Some questions about choose-completion-string-functions)
Date: Wed, 10 Apr 2019 11:48:27 +0300

On April 10, 2019 11:39:55 AM GMT+03:00, Andreas Schwab <schwab <at> suse.de> wrote:
> On Apr 10 2019, Eli Zaretskii <eliz <at> gnu.org> wrote:
> 
> > On April 10, 2019 11:05:02 AM GMT+03:00, Andreas Schwab
> <schwab <at> suse.de> wrote:
> >> On Apr 10 2019, Eli Zaretskii <eliz <at> gnu.org> wrote:
> >> 
> >> > Unfortunately, that ship has sailed, since within an hour of RC
> >> release a new commit was pushed to the release branch, and another
> one
> >> a week later, without asking.  So now the RC tarball will not be
> able
> >> to be renamed anyway, and the rationale for withholding doc changes
> is
> >> null and void.
> >> 
> >> Why not?  Just tag the last commit that is contained in the rc
> >> release.
> >> 
> >> Andreas.
> >
> > The RC contains several uncommitted changes.  Hopefully won't happen
> in the future.
> 
> That isn't a problem either.  They can be put on a local branch, into
> which upstream is merged after the tag.
> 
> Andreas.

I decided it wasn't worth the hassle of releasing 26.2 from a side branch.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.