From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: schwab@suse.de, eggert@cs.ucla.edu, rgm@gnu.org,
deng@randomsample.de, emacs-devel@gnu.org
Subject: Re: make change-history on non-master branches
Date: Fri, 20 Nov 2015 10:09:03 +0200 [thread overview]
Message-ID: <83mvu96qjk.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0STVxLUPE5wQ875n=7_UQU7OAkRXVzp0PnAsXuobp6ETnA@mail.gmail.com>
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Fri, 20 Nov 2015 01:31:58 +0100
> Cc: David Engster <deng@randomsample.de>, schwab@suse.de, Paul Eggert <eggert@cs.ucla.edu>,
> Emacs developers <emacs-devel@gnu.org>, Glenn Morris <rgm@gnu.org>
>
> Whoever has an habit of looking at the results and makes corrections (or at
> least one specific instance of that "whoever") could refrain of doing so during
> the pretest if it makes life easier for the whoevers who merge the branches.
Alas, it's not just the pretest, it's the entire life time of the
release branch. That life time is just starting for the emacs-25
branch; I'm quite certain that at lease Emacs 25.2 and probably also
25.3 will be delivered from that branch. That's another 2 years. I
don't think we want to wait that long for your useful corrections and
general loving care of ChangeLog.2 ;-)
I hope we will find a better solution to this.
next prev parent reply other threads:[~2015-11-20 8:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 2:15 make change-history on non-master branches Glenn Morris
2015-11-15 7:11 ` Paul Eggert
2015-11-16 16:02 ` Eli Zaretskii
2015-11-18 18:10 ` Glenn Morris
2015-11-18 18:19 ` Eli Zaretskii
2015-11-18 18:28 ` Glenn Morris
2015-11-18 18:46 ` Eli Zaretskii
2015-11-18 19:36 ` David Kastrup
2015-11-19 8:35 ` Andreas Schwab
2015-11-19 15:49 ` Eli Zaretskii
2015-11-19 16:35 ` Andreas Schwab
2015-11-19 17:02 ` Eli Zaretskii
2015-11-19 19:48 ` David Engster
2015-11-19 20:38 ` Eli Zaretskii
2015-11-19 20:57 ` David Engster
2015-11-20 0:31 ` Juanma Barranquero
2015-11-20 8:09 ` Eli Zaretskii [this message]
2015-11-20 16:38 ` Future release schedules (was: make change-history on non-master branches) John Wiegley
2015-11-20 18:04 ` Eli Zaretskii
2015-11-20 18:15 ` Future release schedules John Wiegley
2015-11-20 18:41 ` Future release schedules (was: make change-history on non-master branches) Artur Malabarba
2015-11-20 18:43 ` Artur Malabarba
2015-11-20 18:49 ` Eli Zaretskii
2015-11-20 19:05 ` Eli Zaretskii
2015-11-20 19:14 ` Future release schedules John Wiegley
2015-11-20 21:16 ` Eli Zaretskii
2015-11-20 21:33 ` John Wiegley
2015-11-21 11:14 ` Eli Zaretskii
2015-11-18 19:22 ` make change-history on non-master branches Eli Zaretskii
2015-11-18 20:38 ` Glenn Morris
2015-12-20 18:53 ` Glenn Morris
2015-12-20 21:21 ` Paul Eggert
2015-12-21 0:30 ` Glenn Morris
2015-12-23 1:12 ` John Wiegley
2015-12-23 7:58 ` Paul Eggert
2016-01-25 16:55 ` Glenn Morris
2016-01-25 17:22 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mvu96qjk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=deng@randomsample.de \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=rgm@gnu.org \
--cc=schwab@suse.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).