From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eric@ericabrahamsen.net, Noam Postavsky <npostavs@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Branch freezing for release
Date: Wed, 10 Apr 2019 17:59:14 +0100 [thread overview]
Message-ID: <87pnpt4x0d.fsf@tcd.ie> (raw)
In-Reply-To: <83pnpt6cf9.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 10 Apr 2019 19:40:58 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Noam Postavsky <npostavs@gmail.com>
>> Date: Wed, 10 Apr 2019 12:16:35 -0400
>> Cc: Emacs developers <emacs-devel@gnu.org>, Eric Abrahamsen <eric@ericabrahamsen.net>
>>
>> > > 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
next prev parent reply other threads:[~2019-04-10 16:59 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 23:05 bug#34776: 27.0.50; Some questions about choose-completion-string-functions Eric Abrahamsen
[not found] ` <handler.34776.B.155191354931988.ack@debbugs.gnu.org>
2019-03-09 0:05 ` bug#34776: Acknowledgement (27.0.50; Some questions about choose-completion-string-functions) Eric Abrahamsen
2019-03-09 2:07 ` Glenn Morris
2019-03-13 16:51 ` Eric Abrahamsen
2019-04-10 0:03 ` Noam Postavsky
2019-04-10 3:16 ` Eric Abrahamsen
2019-04-10 3:29 ` Glenn Morris
2019-04-10 4:33 ` Eli Zaretskii
2019-04-10 6:35 ` Eric Abrahamsen
2019-04-10 7:01 ` Eli Zaretskii
2019-04-10 7:22 ` Eric Abrahamsen
2019-04-10 7:29 ` Eric Abrahamsen
2019-04-10 8:24 ` Eli Zaretskii
2019-04-10 8:57 ` Branch freezing for release (WAS: bug#34776) Noam Postavsky
2019-04-10 9:21 ` Eli Zaretskii
2019-04-10 16:16 ` Noam Postavsky
2019-04-10 16:40 ` Eli Zaretskii
2019-04-10 16:59 ` Basil L. Contovounesios [this message]
2019-04-10 17:12 ` Branch freezing for release Eli Zaretskii
2019-04-10 17:39 ` Basil L. Contovounesios
2019-04-10 18:31 ` Eli Zaretskii
2019-04-11 14:02 ` Basil L. Contovounesios
2019-04-22 13:03 ` Basil L. Contovounesios
2019-04-22 13:14 ` Eli Zaretskii
2019-04-22 15:18 ` Basil L. Contovounesios
2019-04-10 17:56 ` Stefan Monnier
2019-04-10 18:26 ` Eli Zaretskii
2019-04-10 18:54 ` Stefan Monnier
2019-04-10 19:19 ` Eli Zaretskii
2019-04-10 20:16 ` Dmitry Gutov
2019-04-11 0:12 ` Noam Postavsky
2019-04-11 13:52 ` Eli Zaretskii
2019-04-12 1:03 ` Noam Postavsky
2019-04-12 7:04 ` Eli Zaretskii
2019-04-12 10:18 ` Noam Postavsky
2019-04-12 12:23 ` Stefan Monnier
2019-04-12 12:24 ` Eli Zaretskii
2019-04-12 14:14 ` Dmitry Gutov
2019-04-10 13:14 ` Stefan Monnier
2019-04-10 13:47 ` Andreas Schwab
2019-04-10 15:03 ` Eli Zaretskii
2019-04-10 8:05 ` bug#34776: Acknowledgement (27.0.50; Some questions about choose-completion-string-functions) Andreas Schwab
2019-04-10 8:22 ` Eli Zaretskii
2019-04-10 8:39 ` Andreas Schwab
2019-04-10 8:48 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnpt4x0d.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=npostavs@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.