From: Bob Proulx <INVALID.NOREPLY@gnu.org>
To: "Bob Proulx" <bob@proulx.com>, "Ludovic Courtès" <ludo@gnu.org>,
guix-devel@gnu.org, savannah-help-public@gnu.org
Subject: [sr #108565] Send Git commit notifications for dmd to guix-commits@gnu.org
Date: Mon, 12 May 2014 01:29:52 +0000 [thread overview]
Message-ID: <20140511-192952.sv744.93074@savannah.gnu.org> (raw)
In-Reply-To: <20140509-085638.sv15145.91695@savannah.gnu.org>
Update of sr #108565 (project administration):
Status: None => Done
Assigned to: None => rwp
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
Done.
Recently people have been preferring the git_multimail.py notifications over
the previous flavor.
https://github.com/mhagger/git-multimail
That is what I set up by default when this is requested now. You can see an
example of this type of output in the emacs-elpa-diffs archive here.
http://lists.gnu.org/archive/html/emacs-elpa-diffs/2014-05/threads.html
If you don't like that then I can set up the other git post receive
notification hook. But if you do then this is a nice time to change both over
to the new style.
Would you like me to change guix-commits over to the git_multimail style
notification too so that they will be the same as each other? I am trying to
keep most things all doing the same thing so it would be nice from my
perspective to do this conversion so that all are the same, but not critical.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/support/?108565>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next prev parent reply other threads:[~2014-05-12 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 8:56 [sr #108565] Send Git commit notifications for dmd to guix-commits@gnu.org Ludovic Courtès
2014-05-12 1:29 ` Bob Proulx [this message]
2014-05-12 8:04 ` Ludovic Courtès
2014-10-28 23:42 ` Ludovic Courtès
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=20140511-192952.sv744.93074@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bob@proulx.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=savannah-help-public@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/guix.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.