From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 19113@debbugs.gnu.org
Subject: bug#19113: Generate a ChangeLog file from commit logs
Date: Fri, 30 Jan 2015 11:34:10 -0500 [thread overview]
Message-ID: <jwvbnlgjkkz.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <54B86916.2080402@cs.ucla.edu> (Paul Eggert's message of "Thu, 15 Jan 2015 17:27:50 -0800")
> I was planning to do a merge, yes. My thought was to install the changes in
> emacs-24 and then skip them when merging to master, as there's a separate
> set of changes prepared for master.
Could we simply only make the change on master, and keep using the
ChangeLog files in `emacs-24'?
This would decouple this change from the schedule of the Emacs-24.5
release, which I think would be good. Then we could make the change on
Valentine's day.
Stefan
next prev parent reply other threads:[~2015-01-30 16:34 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 23:57 bug#19113: Generate a ChangeLog file from commit logs Paul Eggert
2014-11-20 15:51 ` Eli Zaretskii
2014-11-20 17:43 ` Paul Eggert
2014-11-20 17:44 ` Paul Eggert
2014-11-26 5:38 ` Paul Eggert
2014-11-26 6:21 ` Jan D.
2014-11-26 7:50 ` Paul Eggert
2014-11-26 15:12 ` Stefan Monnier
2014-11-26 19:16 ` Paul Eggert
2014-11-26 22:15 ` Stefan Monnier
2014-12-05 8:07 ` Glenn Morris
2014-12-05 8:38 ` Eli Zaretskii
2014-12-05 14:33 ` Ted Zlatanov
2014-12-05 18:49 ` Stefan Monnier
2014-12-05 20:08 ` Ted Zlatanov
2014-12-06 4:59 ` Stefan Monnier
2014-12-06 13:17 ` Ted Zlatanov
2014-12-06 2:27 ` Dmitry Gutov
2014-12-06 5:06 ` Stefan Monnier
2014-12-06 7:26 ` Eli Zaretskii
2014-12-09 13:46 ` Dmitry Gutov
2014-12-06 10:08 ` Patch queue management systems Eli Zaretskii
2014-12-06 13:12 ` Ted Zlatanov
2014-12-08 21:49 ` Thomas Koch
2014-12-08 23:10 ` Lars Magne Ingebrigtsen
2014-12-09 0:00 ` Lars Magne Ingebrigtsen
2014-12-09 0:32 ` Lars Magne Ingebrigtsen
2014-12-09 2:57 ` Stefan Monnier
2014-12-09 3:16 ` Lars Magne Ingebrigtsen
2014-12-09 12:37 ` Dmitry Gutov
2014-12-09 17:20 ` Lars Magne Ingebrigtsen
2014-12-09 20:40 ` Dmitry Gutov
2014-12-09 20:44 ` Lars Magne Ingebrigtsen
2014-12-09 21:32 ` Dmitry Gutov
2014-12-09 21:58 ` Lars Magne Ingebrigtsen
2014-12-09 21:57 ` Lars Magne Ingebrigtsen
2014-12-10 14:35 ` Ted Zlatanov
2014-12-08 22:24 ` Lars Magne Ingebrigtsen
2014-12-08 22:54 ` joakim
2014-12-09 5:31 ` Ivan Andrus
2014-12-09 0:06 ` Thien-Thi Nguyen
2014-12-09 2:54 ` Stefan Monnier
2014-12-09 3:15 ` Lars Magne Ingebrigtsen
2014-12-09 8:13 ` Stephen Leake
2014-12-09 13:03 ` Dmitry Gutov
2014-12-09 17:09 ` Eli Zaretskii
2014-12-09 17:17 ` Dmitry Gutov
2014-12-09 17:36 ` Eli Zaretskii
2014-12-09 19:31 ` Dmitry Gutov
2014-12-10 14:39 ` Ted Zlatanov
2014-12-11 8:59 ` Steinar Bang
2014-12-11 11:52 ` Ted Zlatanov
2014-12-11 12:38 ` Steinar Bang
2014-12-11 14:31 ` Ted Zlatanov
2014-12-11 14:39 ` David Kastrup
2014-12-11 14:50 ` Ted Zlatanov
2014-12-11 14:55 ` Andreas Schwab
2014-12-11 15:00 ` Ted Zlatanov
2014-12-11 15:26 ` David Kastrup
2014-12-11 15:33 ` Ted Zlatanov
2014-12-11 15:49 ` David Kastrup
2014-12-11 15:19 ` David Kastrup
2014-12-11 18:43 ` Achim Gratz
2014-12-05 15:38 ` bug#19113: Generate a ChangeLog file from commit logs Stefan Monnier
2014-12-06 4:42 ` Paul Eggert
2014-12-06 7:40 ` Eli Zaretskii
2014-12-09 5:14 ` Glenn Morris
2014-12-09 6:42 ` Paul Eggert
2015-01-03 1:37 ` Glenn Morris
2014-11-20 18:00 ` Achim Gratz
2014-11-20 17:25 ` Pádraig Brady
2015-01-12 7:38 ` Paul Eggert
2015-01-15 14:58 ` Stefan Monnier
2015-01-15 21:46 ` Glenn Morris
2015-01-16 1:27 ` Paul Eggert
2015-01-30 16:34 ` Stefan Monnier [this message]
2015-01-30 20:14 ` Paul Eggert
2015-01-31 6:33 ` Stefan Monnier
2015-01-31 8:18 ` Paul Eggert
2015-01-31 9:06 ` Andreas Schwab
2015-03-21 2:37 ` Paul Eggert
2015-03-21 8:33 ` Eli Zaretskii
2015-03-21 14:38 ` Stefan Monnier
2015-03-22 23:53 ` Glenn Morris
2015-04-07 7:06 ` Paul Eggert
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=jwvbnlgjkkz.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=19113@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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.