From: "Rüdiger Sonderfeld" <ruediger@c-plusplus.de>
To: 16435@debbugs.gnu.org
Cc: dgutov@yandex.ru
Subject: bug#16435: Missing email notification for commit in ELPA
Date: Tue, 14 Jan 2014 10:12:48 +0100 [thread overview]
Message-ID: <8226108.xsogu8VkBL@descartes> (raw)
In-Reply-To: <87ppnvwb1r.fsf@yandex.ru>
The mail hook was recently changed to the new git-multimail which should send
one message per commit and fix this problem.
https://savannah.gnu.org/support/?108467
Regards,
Rüdiger
On Tuesday 14 January 2014 04:29:36 Dmitry Gutov wrote:
> This one: d3d8e780d8ea77339231e232adefca01d042d927
>
> I've never received a personal email notification (as diff-hl author).
>
> Now that I've looked closely in
> http://lists.gnu.org/archive/html/emacs-elpa-diffs/2013-12/threads.html,
> this commit was hidden among unrelated ones:
> http://lists.gnu.org/archive/html/emacs-elpa-diffs/2013-12/msg00011.html
>
> Which made it nearly impossible to notice even when subscribed to the
> list.
next prev parent reply other threads:[~2014-01-14 9:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1W6lTK-0004ws-UD@fencepost.gnu.org>
2014-01-14 2:29 ` bug#16435: Missing email notification for commit in ELPA Dmitry Gutov
2014-01-14 9:12 ` Rüdiger Sonderfeld [this message]
2014-01-14 14:03 ` Dmitry Gutov
2014-01-14 13:54 ` Barry OReilly
2014-01-14 15:34 ` Dmitry Gutov
2014-01-14 16:15 ` Barry OReilly
2014-01-14 16:16 ` Dmitry Gutov
2014-01-14 22:13 ` Stefan Monnier
[not found] ` <handler.16435.C.139058804223464.notifdonectrl.0@debbugs.gnu.org>
2014-01-25 11:12 ` bug#16435: acknowledged by developer (control message for bug 16435) Dmitry Gutov
2014-01-25 19:59 ` Glenn Morris
2014-01-25 20:21 ` Dmitry Gutov
2016-07-14 1:54 ` npostavs
2016-07-14 2:16 ` Dmitry Gutov
2016-07-14 2:25 ` Noam Postavsky
2020-09-08 14:16 ` Stefan Kangas
2020-09-08 14:19 ` Dmitry Gutov
2020-09-08 14:59 ` Stefan Kangas
2020-09-08 21:55 ` Dmitry Gutov
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=8226108.xsogu8VkBL@descartes \
--to=ruediger@c-plusplus.de \
--cc=16435@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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.