Re: Branch freezing for release

[Basil L. Contovounesios]

Eli Zaretskii <address@hidden> writes:

>> From: Noam Postavsky <address@hidden>
>> Date: Wed, 10 Apr 2019 12:16:35 -0400
>> Cc: Emacs developers <address@hidden>, Eric Abrahamsen <address@hidden>
>> 
>> > > I don't see anything there about not pushing after an RC is made
>> 
>> > There's no need to say anything else, since an RC should be tarred after 
>> > all
>> > its changes are pushed and tagged. That didn't happen this time by 
>> > omission.
>> > We all make mistakes at times.
>> 
>> Ah, I had initially thought you meant the unfortunate mistake was on
>> part of the person/people pushing to emacs-26 after the RC.
>
> If just one of these two things happened -- either they asked whether
> it was okay to push, or the RC was pushed and tagged -- we'd be okay,
> but none of them happened.

Just to be clear: is it okay to push/backport fixes to emacs-26 again?
I've noted the following commits as candidates for backporting:

[1: 10cd65878c]: Update documentation for indent-relative functions
  2019-04-05 19:48:21 -0500
  
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=10cd65878c741d2a22a1f2c36c54fcad4e516f72

[2: 0e468a6204]: Avoid using obsolete indent-relative-maybe
  2019-04-03 17:55:40 +0100
  
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=0e468a620458fecd003c396050aa6deb722982c1

[3: 690c678fb6]: Fix comment-empty-lines docstring (bug#35152)
  2019-04-04 23:41:02 +0100
  
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=690c678fb6c1fb5b2f828f9bb90782bd0b01c399

N.B.: Commit [2] also includes small code changes, not just docfixes.

Thanks,

-- 
Basil