unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: bruce.connor.am@gmail.com
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] master 5515625: ; ChangeLog.2 fixes
Date: Sun, 25 Oct 2015 16:47:15 +0100	[thread overview]
Message-ID: <CAAeL0STghv7jQr-gGCWdFcG0MbAgPozc7fprZ4+2o-CX5+86Ng@mail.gmail.com> (raw)
In-Reply-To: <CAAdUY-L5fXC3KAJ4c0dJvk3tWhOkU4v+ADbxecJeaF2D6NkDgQ@mail.gmail.com>

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

Hi.

The CONTRIBUTE file talks about the commit log messages. We generate the
ChangeLog from the commit messages, but it is its own thing, and I think
that making it more readable, removing redundancies, etc. is good. They
mostly have different targets; we developers are now much more likely to
use git log or gitk than go fishing into ChangeLogs, while people who
downloads a source tarball only has the ChangeLogs. That's why I spend time
cleaning them.

As for that particular example, I've mostly respected cases of "one line
description non-ending in period", but when the one-line description is of
the type

    * file (blabla): some change"

I usually change it to

    * dir/file (blabla): Some change.

for coherence with other entries that do not happen to be the one-line
description of a commit.

I also remove (here and in a patch I'm working on) the one-line description
in cases like:

   Do XXX in function YYY of file ZZZ

   * ZZZ: Do XXX in function YYY.

or

   Do XXX in function YYY of file ZZZ

   * ZZZ(YYY): Do XXX.

but I've left one-line descriptions untouched when they add information or
are formulated differently.

That said, I do these changes that I feel make ChangeLog better, but anyone
is of course entitled to do the same or revert my changes. Or, if there's
some consensus that some of these changes are wrong, I'll adapt to whatever
is preferred.

Thanks,

    Juanma

[-- Attachment #2: Type: text/html, Size: 1905 bytes --]

  reply	other threads:[~2015-10-25 15:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151025140139.5262.2147@vcs.savannah.gnu.org>
     [not found] ` <E1ZqLrf-0001NU-5R@vcs.savannah.gnu.org>
2015-10-25 15:32   ` [Emacs-diffs] master 5515625: ; ChangeLog.2 fixes Artur Malabarba
2015-10-25 15:47     ` Juanma Barranquero [this message]
2015-10-25 19:21       ` Eli Zaretskii
2015-10-25 22:25         ` Juanma Barranquero
2015-10-25 23:56           ` Artur Malabarba

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=CAAeL0STghv7jQr-gGCWdFcG0MbAgPozc7fprZ4+2o-CX5+86Ng@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=bruce.connor.am@gmail.com \
    --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 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).