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: Wed, 01 Sep 2010 06:18:22 -0500 [thread overview]
Message-ID: <87occhd85d.fsf@lifelogs.com> (raw)
In-Reply-To: <87iq2prjr0.fsf@marauder.physik.uni-ulm.de>
On Wed, 01 Sep 2010 09:44:03 +0200 Reiner Steib <reinersteib+gmane@imap.cc> wrote:
RS> - "From: www-data ..." is useless. I want the person who committed
RS> (pushed?) the change.
Done.
The cvslog post gets moderated because of this changed:
"Your message to ding-cvslog has been delayed, and requires the approval
of the moderators"
so using the real author e-mail will require more work for the
moderator. We could use the comitter instead to make it less variable
but I think you want the author, right?
RS> - "Subject: [git] Gnus Project branch, master, updated. [some_long_hash]"
RS> Please show the file names and the "one line summary" when possible.
There can be many files. Better to just show the one-line summary
(showing just one file when possible creates inconsistent output so I
thought it wasn't optimal). If you want it otherwise, see below.
RS> - Could the boilerplate text[1] be appended instead of putting it at
RS> the top of the message?
Done.
RS> What happened to ding-patches (gmane.emacs.gnus.commits)? No postings
RS> since April 2010.
RS> With CVS, ding-cvslog (gmane.emacs.gnus.cvs) showed only a summary
RS> (e.g. http://article.gmane.org/gmane.emacs.gnus.cvs/9382) and
RS> ding-patches (gmane.emacs.gnus.commits) included the diff output as
RS> well.
Tell me how you want it to work. For me the current situation is OK.
The posts get gatewayed to the mailing lists on quimby (listed below)
and I have never needed just the summary.
The changes mentioned above required the standard
git-core/post-receive-email, which I modified and configured so:
[hooks]
mailinglist = cvslog@quimby.gnus.org,ding-commits@quimby.gnus.org,tzz@lifelogs.com
emailprefix = "[git] "
envelopesender = git-logger
showrev = "git show -C %s; echo"
The modified post-receive hook is under etc/post-receive in Git now. So
you can look in there and make modifications (list files in the subject,
etc). I can test and install them into gnus.git/hooks/post-receive on
the server. We can also put the Git repo config file in the repo
(partially cited above) if you think it's necessary.
Ted
next prev parent reply other threads:[~2010-09-01 11:18 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 [this message]
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
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=87occhd85d.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).