From: Stefan Kangas <stefan@marxist.se>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 16435@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#16435: acknowledged by developer (control message for bug 16435)
Date: Tue, 8 Sep 2020 14:16:21 +0000 [thread overview]
Message-ID: <CADwFkmmdAAsGvqjf3vgz+R9u54n=azQ-ooD77zfBX=DUFEy-cg@mail.gmail.com> (raw)
In-Reply-To: <72e6aa79-2b71-8425-6882-28f0228c6e1f@yandex.ru> (Dmitry Gutov's message of "Thu, 14 Jul 2016 05:16:59 +0300")
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 07/14/2016 04:54 AM, npostavs@users.sourceforge.net wrote:
>
>> This is fixed now, right? I've received some diffs for yasnippet.
>
> Not sure it's working properly. I've received four emails for Paul's f105338
> commit, but all of them were addressed to emacs-elpa-diffs (I'm subscribed to
> it, so I can't tell if any of them had me in BCC).
>
> And three of them were the same, a truncated version of the fourth that stopped
> at 268th line.
Is this still an issue?
next prev parent reply other threads:[~2020-09-08 14:16 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
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 [this message]
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='CADwFkmmdAAsGvqjf3vgz+R9u54n=azQ-ooD77zfBX=DUFEy-cg@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=16435@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=npostavs@users.sourceforge.net \
/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.