From: Nicolas Richard <youngfrog@members.fsf.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 21107-done@debbugs.gnu.org
Subject: bug#21107: Processed: control message for bug #16785
Date: Fri, 24 Jul 2015 07:19:38 +0200 [thread overview]
Message-ID: <86mvymm8t1.fsf@members.fsf.org> (raw)
In-Reply-To: <vamvymej9g.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu, 23 Jul 2015 16:00:59 -0400")
Glenn Morris <rgm@gnu.org> writes:
> Nicolas Richard wrote:
>> What's the proper way to fix my mistake ?
>
> Just close either 16785 or 21107.
Ok done, thanks.
Nicolas.
prev parent reply other threads:[~2015-07-24 5:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871tfz87yq.fsf@members.fsf.org>
[not found] ` <handler.s.C.143764856322041.transcript@debbugs.gnu.org>
2015-07-23 16:09 ` bug#21107: Processed: control message for bug #16785 Glenn Morris
2015-07-23 19:36 ` Nicolas Richard
2015-07-23 20:00 ` Glenn Morris
2015-07-24 5:19 ` Nicolas Richard [this message]
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=86mvymm8t1.fsf@members.fsf.org \
--to=youngfrog@members.fsf.org \
--cc=21107-done@debbugs.gnu.org \
--cc=rgm@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 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).