From: Glenn Morris <rgm@gnu.org>
To: Joseph Mingrone <jrm@ftfl.ca>
Cc: 28464@debbugs.gnu.org
Subject: bug#28464: 25.3; regression in erc track notifications after upgrading to 25.3.1
Date: Thu, 14 Sep 2017 16:45:52 -0400 [thread overview]
Message-ID: <4ntw05dn5r.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <86y3phawka.fsf@phe.ftfl.ca> (Joseph Mingrone's message of "Thu, 14 Sep 2017 16:51:01 -0300")
It is difficult to see how this could be, because there were literally
zero changes between 25.2 and 25.3 except for those related to
the enriched issue.
next prev parent reply other threads:[~2017-09-14 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 19:51 bug#28464: 25.3; regression in erc track notifications after upgrading to 25.3.1 Joseph Mingrone
2017-09-14 20:45 ` Glenn Morris [this message]
2017-09-14 20:47 ` Joseph Mingrone
2017-09-16 8:00 ` Nicolas Petton
2017-09-16 16:22 ` Joseph Mingrone
2017-09-16 18:10 ` Nicolas Petton
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ntw05dn5r.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=28464@debbugs.gnu.org \
--cc=jrm@ftfl.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).