unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: romain@orebokech.com, emacs-devel@gnu.org
Subject: Re: Header lines of commit messages
Date: Sun, 27 Jun 2010 02:08:37 +0900	[thread overview]
Message-ID: <87eiftn2lm.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <83eiftddbj.fsf@gnu.org>

Eli Zaretskii writes:
 > > From: "Stephen J. Turnbull" <stephen@xemacs.org>
 > >  > 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.

You're missing the point.  Romain and the org-mode community are
responsible for org-mode most of the time, until it becomes Stefan's/
Yidong's baby in the run-up to a release.  Either way, it should not
affect any of the things you are interested in, so you just don't want
to know.  You want your eyes to glide right over "org-mode synch to
git commit ABCDEF" just as it does over "Gnus synch."  Life is too
short to even think about that stuff.  Put it this way: what could
Romain have written there that would cause you to want to read the
whole commit message?

If you really *do* want to know about irrelevant commits, I don't
understand why you find it acceptable that Gnus doesn't rebase its
synchs into the mainline.  After all, Gnus contains message-mode, and
that does affect your life since message-mode is proposed as a
replacement for RMail's composition mode, a replacement you don't yet
consider acceptable.  So what exactly is happening in Gnus is in fact
relevant to you; even I know that.  Why don't you complain about that?
Presumably because *there are too many irrelevant commits* compressed
into those merges, and you are forced to the conclusion that reading
them would be a waste of your time, and a waste of the committer's
time to rebase them onto the mainline.

Well, the org-mode synch is just as irrelevant.

 > > 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.

You think you do, but that's just an unproductive habit, as shown by
the fact that you don't have a problem with the Gnus merge messages.

Also, by "who" I mean which subprojects, not which developers.



  reply	other threads:[~2010-06-26 17:08 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
2010-06-26 17:08       ` Stephen J. Turnbull [this message]
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=87eiftn2lm.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=romain@orebokech.com \
    /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).