all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: ChangeLog entries
Date: Mon, 10 Aug 2015 10:16:55 +0100	[thread overview]
Message-ID: <8737zrijug.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <83r3ncpbhv.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 9 Aug 2015 21:23:08 +0300")




Eli Zaretskii <eliz@gnu.org> writes:

>> From: phillip.lord@russet.org.uk (Phillip Lord)
>> Cc: <emacs-devel@gnu.org>
>> Date: Sun, 09 Aug 2015 16:46:20 +0100
>> 
>> They are both changes to trunk. feadec was a change *originally* made on
>> a branch, 45987 is a merge commit pulling feadec onto trunk also. I
>> wanted Nicolas to okay by change given that it was his code.
>
> Then please in the future use the format we follow, which is identical
> to ChangeLog entries: a function name in parentheses followed by the
> description of what changes were made in that function.

Ah, okay, will do that in future.


>
>> I'd rather feadec wasn't deleted. It's my first ChangeLog entry and I'm
>> really rather proud of it, pathetic as that might sound.
>
> I'm only talking about the form, not about the contents.  I suggest to
> edit ChangeLog.2 to make this entry into its correct form, and commit
> the change.

Is the ChangeLog not autogenerated from the commit message? This is what
I had assumed. I can change the ChangeLog.2 without changing the commit
message?

Phil



  reply	other threads:[~2015-08-10  9:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-09 15:11 ChangeLog entries Eli Zaretskii
2015-08-09 15:46 ` Phillip Lord
2015-08-09 18:23   ` Eli Zaretskii
2015-08-10  9:16     ` Phillip Lord [this message]
2015-08-10  9:37       ` Artur Malabarba
2015-08-10 11:55         ` Phillip Lord
2015-08-10 13:02   ` Nicolas Petton
2015-08-10 17:19     ` Eli Zaretskii
2015-08-10 21:17       ` Paul Eggert
2015-08-10 21:54       ` Phillip Lord
2015-08-09 16:05 ` Paul Eggert
2015-08-09 18:24   ` 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=8737zrijug.fsf@newcastle.ac.uk \
    --to=phillip.lord@newcastle.ac.uk \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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.