From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: 21998@debbugs.gnu.org
Subject: bug#21998: Run 'make change-history' on release branch
Date: Fri, 11 Mar 2016 10:48:43 +0200 [thread overview]
Message-ID: <83vb4tjt78.fsf@gnu.org> (raw)
In-Reply-To: <E1ae83h-0000p5-Vl@fencepost.gnu.org> (message from Richard Stallman on Thu, 10 Mar 2016 16:23:49 -0500)
> From: Richard Stallman <rms@gnu.org>
> CC: rgm@gnu.org, 21998@debbugs.gnu.org
> Date: Thu, 10 Mar 2016 16:23:49 -0500
>
> > But as soon as we started to work on both master and the release
> > branch, this broke down because merges from the release branch to
> > master don't live well with the manual corrections. This was never
> > fixed because there appears to be no motivation for fixing it.
>
> Maybe this discussion gives people the motivation to fix it.
I hope so.
> Is there a clear path for fixing it?
Not yet, AFAICT.
next prev parent reply other threads:[~2016-03-11 8:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 19:08 bug#21998: Run 'make change-history' on release branch Glenn Morris
2016-02-13 0:52 ` Paul Eggert
2016-02-16 16:41 ` Glenn Morris
2016-02-16 17:54 ` Paul Eggert
2016-03-04 16:46 ` Glenn Morris
2016-03-05 19:11 ` Eli Zaretskii
2016-03-06 9:47 ` Lars Magne Ingebrigtsen
2016-03-06 18:02 ` Dmitry Gutov
2016-03-06 21:07 ` John Wiegley
2016-03-06 21:25 ` Ingo Lohmar
2016-03-06 21:52 ` bug#21998: Is it time to drop ChangeLogs? (Was: bug#21998: Run 'make change-history' on release branch) John Wiegley
[not found] ` <m2oaarxojf.fsf_-_@newartisans.com>
2016-03-06 22:05 ` Eric S. Raymond
2016-03-06 22:34 ` Paul Eggert
2016-03-06 23:06 ` Drew Adams
[not found] ` <64a52598-ad53-498c-993c-67d7827dbdfc@default>
2016-03-07 0:15 ` bug#21998: Is it time to drop ChangeLogs? John Wiegley
[not found] ` <m2io0zw3cd.fsf@newartisans.com>
2016-03-07 0:24 ` Drew Adams
2016-03-07 0:22 ` Mathieu Lirzin
[not found] ` <87vb4zb0i4.fsf@gnu.org>
2016-03-07 1:19 ` Eric S. Raymond
2016-03-07 9:29 ` Alan Mackenzie
[not found] ` <56DCB064.9060206@cs.ucla.edu>
2016-03-07 16:26 ` bug#21998: Is it time to drop ChangeLogs? (Was: bug#21998: Run 'make change-history' on release branch) Eli Zaretskii
2016-03-08 7:32 ` bug#21998: Run 'make change-history' on release branch Glenn Morris
2016-03-08 16:08 ` Eli Zaretskii
2016-03-07 6:51 ` Richard Stallman
2016-03-07 16:02 ` Eli Zaretskii
2016-03-07 16:35 ` John Wiegley
2016-03-07 17:00 ` Eli Zaretskii
2016-03-07 17:51 ` John Wiegley
2016-03-08 18:23 ` Richard Stallman
2016-03-08 18:30 ` Eli Zaretskii
2016-03-09 16:38 ` Richard Stallman
2016-03-09 16:51 ` Eli Zaretskii
2016-03-10 21:23 ` Richard Stallman
2016-03-11 8:48 ` Eli Zaretskii [this message]
2016-03-11 10:05 ` Nicolas Petton
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=83vb4tjt78.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21998@debbugs.gnu.org \
--cc=rms@gnu.org \
/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).