From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Git, ding-cvslog (gmane.emacs.gnus.cvs), ding-patches (gmane.emacs.gnus.commits)
Date: Thu, 02 Sep 2010 05:05:47 -0500 [thread overview]
Message-ID: <877hj4cves.fsf@lifelogs.com> (raw)
In-Reply-To: <m3zkw0luna.fsf@quimbies.gnus.org>
On Thu, 02 Sep 2010 04:57:29 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> OK, now post-receive will merge multiple commit messages into one long
>> subject line and format the message as Adam proposed. Changes are in
>> etc/post-receive and comitted.
LMI> They now look like this:
LMI> Subject: [git] Gnus Project branch, master, updated. 56bbe449783867ec4d9d92387172383531ead4ec Remove %O (moderated) from group line format, since it isn't very interesting.
LMI> Isn't the first bit kinda not very interesting to humans? I mean the
LMI> "[git] Gnus Project branch, master, updated. 56bbe449783867ec4d9d92387172383531ead4ec"
LMI> bit. Does that have to be in the Subject header? Perhaps just "Gnus
LMI> Project" is sufficient?
The branch is necessary. "updated" denoted the action taken. The [git]
prefix is, I think, a nice visual filter (especially since we set the
sender to the author). "Gnus Project" is the Git repo's config
description which we know. The revision ID could be omitted, sure. So
maybe this is better.
Subject: [gnus git] master updated. Remove %O (moderated) from group line format, since it isn't very interesting.
I made the change after my last commit so the next push will show the
new format.
One inaccuracy is that with multiple authors, only the most recent one
is used, and perhaps the comitter is the right name to put in From
instead of the author. OTOH when Katsumi synchronizes, it's better to
see who made the change originally. I'm open to suggestions.
Ted
next prev parent reply other threads:[~2010-09-02 10:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 7:44 Reiner Steib
2010-09-01 11:18 ` Ted Zlatanov
2010-09-01 11:21 ` Ted Zlatanov
2010-09-01 14:36 ` Jason L Tibbitts III
2010-09-01 20:22 ` Adam Sjøgren
2010-09-01 20:28 ` Lars Magne Ingebrigtsen
2010-09-02 2:42 ` Ted Zlatanov
2010-09-02 2:57 ` Lars Magne Ingebrigtsen
2010-09-02 10:05 ` Ted Zlatanov [this message]
2010-09-02 10:55 ` Adam Sjøgren
2010-09-02 12:31 ` Ted Zlatanov
2010-09-02 14:28 ` Lars Magne Ingebrigtsen
2010-09-01 20:30 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877hj4cves.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).