all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: Header lines of commit messages
Date: Thu, 01 Jul 2010 08:02:27 -0500	[thread overview]
Message-ID: <87mxub5p98.fsf@lifelogs.com> (raw)
In-Reply-To: 83zkyc9qjg.fsf@gnu.org

On Thu, 01 Jul 2010 00:08:51 +0300 Eli Zaretskii <eliz@gnu.org> wrote: 

EZ> As long as you are committing to the Emacs repository many unrelated
EZ> changes, there really is no way of making the commit messages more
EZ> useful.  But at least in several cases, it looks like the committed
EZ> changes belong to a single changeset.  Examples:
...
EZ> For such changes, it would be more useful if the first line of the
EZ> commit message summarized the change, instead of saying just "Synch
EZ> with Gnus trunk".  That would allow to, e.g., find the merge which
EZ> introduced some specific change in Gnus by just looking at the output
EZ> of "bzr log --line", which shows only those first lines from the
EZ> commit messages.

Thanks for explaining.  The Gnus developers will try to make these
commits look better in the --line format and we'll see if we can make
the synchronization happen for every commit instead of batched.

Ted




      reply	other threads:[~2010-07-01 13:02 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
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 [this message]

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=87mxub5p98.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.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.