unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
	Emacs Development <Emacs-devel@gnu.org>
Subject: Re: April 7 cutover for generating ChangeLog automatically
Date: Tue, 7 Apr 2015 15:05:47 +0100	[thread overview]
Message-ID: <CALDnm52EXkVm0FBpPXRAA_9QGar0KJ3vbMyZLPgPBd6vth_VhA@mail.gmail.com> (raw)
In-Reply-To: <5523DA83.2000607@yandex.ru>

On Tue, Apr 7, 2015 at 2:24 PM, Dmitry Gutov <dgutov@yandex.ru> wrote:
> Hi Paul,
>
> On 03/31/2015 10:53 AM, Paul Eggert wrote:
>
>> The suggested format for commit messages will be changed slightly:
>>
>>   - File names should be relative to the top level, e.g.:
>
>
> Shouldn't this rule be accompanied with a change in `add-change-log-entry'?
> Or `find-change-log'?

FWIW, If you have the multiple dummy ChangeLog buffers, I think eventually
`log-edit-insert-changelog' does the right thing and inserts the top-level path.

Would be nice to automatically cleanup those buffers though, or not
need  them at all.

-- 
João Távora



  reply	other threads:[~2015-04-07 14:05 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
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 [this message]
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=CALDnm52EXkVm0FBpPXRAA_9QGar0KJ3vbMyZLPgPBd6vth_VhA@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=Emacs-devel@gnu.org \
    --cc=dgutov@yandex.ru \
    --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).