From: Eli Zaretskii <eliz@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: romain@orebokech.com, emacs-devel@gnu.org
Subject: Re: Header lines of commit messages
Date: Sat, 26 Jun 2010 18:27:12 +0300 [thread overview]
Message-ID: <83eiftddbj.fsf@gnu.org> (raw)
In-Reply-To: <87hbkpn8d4.fsf@uwakimon.sk.tsukuba.ac.jp>
> From: "Stephen J. Turnbull" <stephen@xemacs.org>
> Cc: Eli Zaretskii <eliz@gnu.org>,
> emacs-devel@gnu.org
> Date: Sun, 27 Jun 2010 00:04:07 +0900
>
> Romain Francoise writes:
> > Eli Zaretskii <eliz@gnu.org> writes:
> >
> > > The header line that summarizes the commit conveys useless
> > > information.
>
> I would phrase that "the headline conveys the information that
> thinking about this commit is useless to Emacs maintainers."<wink>
> Seriously, you've been describing your information overload in other
> contexts.
Exactly. That is why seeing "cherry-pick commit ABCDEF" means I need
to read the whole commit message, i.e. waste my time, whereas "[merge]
Do not bind obsolete variables." tells it all without any additional
effort.
> Yes, as a member of the project, it's important to have
> some idea of who's active, but the details would just be overload.
Sorry, I'm not following. I didn't want to see the author of the
change, just its essence.
next prev parent reply other threads:[~2010-06-26 15:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 10:43 Header lines of commit messages Eli Zaretskii
2010-06-26 13:33 ` Romain Francoise
2010-06-26 15:01 ` Eli Zaretskii
2010-06-26 15:04 ` Stephen J. Turnbull
2010-06-26 15:27 ` Eli Zaretskii [this message]
2010-06-26 17:08 ` Stephen J. Turnbull
2010-06-26 18:16 ` Eli Zaretskii
2010-06-27 12:36 ` Stephen J. Turnbull
2010-06-30 18:36 ` Ted Zlatanov
2010-06-30 21:08 ` Eli Zaretskii
2010-07-01 13:02 ` Ted Zlatanov
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=83eiftddbj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=romain@orebokech.com \
--cc=stephen@xemacs.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).