all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bruce.connor.am@gmail.com, Emacs developers <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] master 5515625: ; ChangeLog.2 fixes
Date: Sun, 25 Oct 2015 23:25:58 +0100	[thread overview]
Message-ID: <CAAeL0SQrhFG1yCoC-R=HOw4Uy0dnmyHt6_pgnxT1hXVGCYReFA@mail.gmail.com> (raw)
In-Reply-To: <83fv0ydaap.fsf@gnu.org>

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

On Sun, Oct 25, 2015 at 8:21 PM, Eli Zaretskii <eliz@gnu.org> wrote:

> That's correct.  Personally, I think the commit messages themselves
> could have the period in this special case, but that's just MO.

I agree.

> This is borderline, and you might as well leave those untouched.

The ones I change tend to be like

        Use `unless' to have one fewer `not'
        * lisp/vc/vc-git.el (vc-git-resolve-when-done): Use `unless' to
        have one fewer `not'.

or

        Fix customization type of `even-window-sizes'.
        * lisp/window.el (even-window-sizes): Fix customization type.

where, really, the header doesn't add anything of value (to the ChangeLog).

> These are issues of style, so there are no hard rules.  Back when we
> maintained ChangeLog files by hand the style was not really uniform,
> either.

Yes, I know. I didn't try then, and do not try now, to have absolute
consistency, just to increment it a little ;-)

>   +       * lisp/character-fold.el: Many improvements.
>           (character-fold-search-forward, character-fold-search-backward):
>   -       New command

> The "many improvements" part could simply go away, it doesn't add any
> useful information.

I'd tend to agree, but I'm conservative in removing other people's words
unless they are really redundant (as in the cases above).

> I think the commit message should have been as corrected to begin
> with, and a header line should say something else, without being
> formatted as an entry.

Certainly. The best messages IMHO are those who do *not* format the header
line as an entry. They are usually more informative and less redundant.

> This is okay, but when I see such changes, I always ask myself whether
> it's worth the trouble.  Your call.

Some of these are because I use column markers to see which entries go over
75 or 80 columns, and some because I agree with Stefan that having dangling
words is ugly. Which doesn't mean that I don't leave some of these, when
the alternative is equally ugly, of course...

>    2015-10-20  Dmitry Gutov  <dgutov@yandex.ru>
>
>   -       Don't declare vc-exec-after anymore
>   -
>           * lisp/vc/vc-svn.el:
>           * lisp/vc/vc-mtn.el:
>           * lisp/vc/vc-hg.el:
>           * lisp/vc/vc-cvs.el:
>           * lisp/vc/vc-git.el:
>   -       * lisp/vc/vc-bzr.el: Don't declare vc-exec-after anymore.  Its
>   -       usages have been replaced with vc-run-delayed.
>   +       * lisp/vc/vc-bzr.el: Don't declare vc-exec-after anymore.
>   +       Its usages have been replaced with vc-run-delayed.
>
> Not sure why the header line was deleted, it looks OK to me.

Borderline, but the header is duplicated word-for-word in the entry. I
think I would've left it if the file list were quite long.

Thanks for your comments.

     J

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

  reply	other threads:[~2015-10-25 22:25 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
2015-10-25 19:21       ` Eli Zaretskii
2015-10-25 22:25         ` Juanma Barranquero [this message]
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

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

  git send-email \
    --in-reply-to='CAAeL0SQrhFG1yCoC-R=HOw4Uy0dnmyHt6_pgnxT1hXVGCYReFA@mail.gmail.com' \
    --to=lekktu@gmail.com \
    --cc=bruce.connor.am@gmail.com \
    --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.