From: Carlos Pita <carlosjosepita@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: Misbehaving gnus-gcc-mark-as-read while archiving to current group
Date: Tue, 12 Aug 2014 19:02:24 -0300 [thread overview]
Message-ID: <84ppg5icy7.fsf@gmail.com> (raw)
In-Reply-To: <8761hxk4z6.fsf@debian.uxu>
> I've reported this as a bug a number of days ago, and I would like to
> add the above remark as a followup or commentary to the report, but I'm
> not able to find instructions on how to do that.
Ok, I finally found out how to do this. The automatic ack that is send
just after reporting a bug contains instructions (the usual debbugs
ones) to submit further information: just send an email to
NNNNN@debbugs.gnu.org, where NNNNN is the bug number (also reported in
the ack email).
I've deleted the ack the first time so I was clueless after that.
Cheers
--
Carlos
next prev parent reply other threads:[~2014-08-12 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 15:38 Carlos Pita
2014-08-05 22:41 ` Emanuel Berg
2014-08-12 16:28 ` Carlos Pita
2014-08-12 17:11 ` Emanuel Berg
2014-08-12 22:02 ` Carlos Pita [this message]
2014-08-12 22:25 ` Emanuel Berg
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=84ppg5icy7.fsf@gmail.com \
--to=carlosjosepita@gmail.com \
--cc=info-gnus-english@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.
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).