unofficial mirror of emacs-devel@gnu.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: Wed, 30 Jun 2010 13:36:13 -0500	[thread overview]
Message-ID: <87aaqc9xlu.fsf@lifelogs.com> (raw)
In-Reply-To: 838w61d5gs.fsf@gnu.org

On Sat, 26 Jun 2010 21:16:51 +0300 Eli Zaretskii <eliz@gnu.org> wrote: 

EZ> In the Gnus case, I'd prefer more meaningful headers as well, but it's
EZ> hard to ask for that when a large body of unrelated changes is
EZ> delivered to Emacs at once.

Katsumi Yamaoka has been doing the synchronization so far.  Let him and
the other Gnus developers know if there's a problem with the
synchronization log messages.

I plan to eventually set up a more automatic synchronization method.

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

EZ> Because I'm too old to fight Quixotic battles.  And because people who
EZ> do the job should have some leeway in determining how far they want to
EZ> go towards the project to which they contribute.  If Stefan and Yidong
EZ> can live with what Gnus maintainers do when they synch, so can I.

Sorry, I am not clear on the problem, though it's probably obvious to
you.  Can you explain what's the problem and what we can do on the Gnus
side to remedy it?

Thanks
Ted




  parent reply	other threads:[~2010-06-30 18:36 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 [this message]
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=87aaqc9xlu.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 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).