all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: make change-history on non-master branches
Date: Sat, 14 Nov 2015 23:11:39 -0800	[thread overview]
Message-ID: <5648302B.30903@cs.ucla.edu> (raw)
In-Reply-To: <l3a8qg6m8y.fsf@fencepost.gnu.org>

Glenn Morris wrote:
> Why does 'make change-history' refuse to run on non-master branches?
> It's going to need to be run on the emacs-25 branch, isn't it?

'make change-history' refuses to run on non-master branches because I thought 
there would be problems if people ran it on their own branches.  Feel free to 
remove that check if you want to deal with the fallout.

> (It seems to me that it would be simpler if the corrections to commit
> logs were versioned, not the whole generated ChangeLog; but I've said
> that before.)

That's what coreutils does.  Only one person uses that facility, which is hard 
to use, and my impression is that nobody else understands how it works.



  reply	other threads:[~2015-11-15  7:11 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5648302B.30903@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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 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.