unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Petton <nicolas.petton@foretagsplatsen.se>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Emacs Development <Emacs-devel@gnu.org>
Subject: Re: April 7 cutover for generating ChangeLog automatically
Date: Tue, 31 Mar 2015 16:07:08 +0200	[thread overview]
Message-ID: <87a8yt2rcj.fsf@foretagsplatsen.se> (raw)
In-Reply-To: <551A528C.7080008@cs.ucla.edu>

[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]

Paul Eggert writes:

> Currently, each Emacs commit typically contains two copies of its ChangeLog 
> entries: one copy in the commit message and one copy as an edit to one or more 
> ChangeLog files.  The latter copy is largely redundant and complicates merging, 
> so as discussed in Bug#19113 on April 7 we plan to revamp the Emacs master 
> commit procedure to eliminate the second copy, so that ordinary commits do not 
> alter ChangeLog files.  Instead, the ChangeLog file in the Emacs distribution 
> will be generated automatically from recent Git commit messages.
>
> You'll still be able to edit ChangeLog history by running 'make change-history' 
> and then committing changes to a new top-level file (initially 'ChangeLog.1') 
> that contains an editable copy of non-recent Git commit messages.  However, 
> commits ordinarily shouldn't change ChangeLog files and this should simplify 
> merging.

Does it mean that the ChangeLog files won't be updated anymore or that
they will be updated only from time to time (like right before a release
or something like that)?

Also, I think that admin/make-tarball.txt will have to be updated.

Cheers,
Nico
-- 
Nicolas Petton
http://nicolas-petton.fr

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 512 bytes --]

  parent reply	other threads:[~2015-03-31 14:07 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31  7:53 April 7 cutover for generating ChangeLog automatically Paul Eggert
2015-03-31 11:58 ` Eli Zaretskii
2015-03-31 12:57   ` Stefan Monnier
2015-03-31 13:04     ` Eli Zaretskii
2015-03-31 20:49       ` Stefan Monnier
2015-04-01  2:37         ` Eli Zaretskii
2015-03-31 14:07 ` Nicolas Petton [this message]
2015-03-31 18:17   ` Paul Eggert
2015-03-31 21:35     ` nicolas.petton
2015-04-01  4:59       ` Paul Eggert
2015-03-31 21:52     ` Nicolas Petton
2015-03-31 14:45 ` Dmitry Gutov
2015-03-31 17:56   ` Paul Eggert
2015-03-31 20:52 ` Stefan Monnier
2015-03-31 21:50   ` Dmitry Gutov
2015-04-01  2:21     ` Stefan Monnier
2015-04-07 11:48       ` Dmitry Gutov
2015-04-01  5:13   ` Paul Eggert
2015-04-07  7:19 ` Emacs master ChangeLog files now generated automatically Paul Eggert
2015-04-07 14:04   ` John Wiegley
2015-04-07 16:48     ` Karl Fogel
2015-04-07 13:24 ` April 7 cutover for generating ChangeLog automatically Dmitry Gutov
2015-04-07 14:05   ` João Távora
2015-04-07 14:27     ` Eli Zaretskii
2015-04-07 16:41       ` Paul Eggert
2015-04-07 17:25       ` Dmitry Gutov
2015-04-07 17:32         ` Eli Zaretskii
2015-04-07 18:16           ` Dmitry Gutov
2015-04-07 18:27             ` Eli Zaretskii
2015-04-07 20:09               ` Paul Eggert
2015-04-08  5:36                 ` Eli Zaretskii
2015-04-08 15:07                   ` Dmitry Gutov
2015-04-08 15:18                     ` Eli Zaretskii
2015-04-08 15:31                       ` Dmitry Gutov
2015-04-08 15:37                         ` Eli Zaretskii
2015-04-08 16:08                           ` Eli Zaretskii
2015-04-08 19:15                             ` Stefan Monnier
2015-04-09  0:42                               ` Dmitry Gutov

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=87a8yt2rcj.fsf@foretagsplatsen.se \
    --to=nicolas.petton@foretagsplatsen.se \
    --cc=Emacs-devel@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 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).