From: Julien Danjou <julien@danjou.info>
To: Antoine Levitt <antoine.levitt@gmail.com>
Cc: ding@gnus.org
Subject: Re: Inconsistent doc for message-generate-new-buffers
Date: Mon, 07 Mar 2011 15:42:15 +0100 [thread overview]
Message-ID: <sa362rvxa9k.fsf@cigue.easter-eggs.fr> (raw)
In-Reply-To: <87d3m3jbbr.fsf@gmail.com> (Antoine Levitt's message of "Mon, 07 Mar 2011 14:43:04 +0100")
[-- Attachment #1: Type: text/plain, Size: 253 bytes --]
On Mon, Mar 07 2011, Antoine Levitt wrote:
> The info doc is out of date.
Merged, but please include a ChangeLog entry next time, it'd be easier
to merge. Git format-patch is welcome also. :)
--
Julien Danjou
❱ http://julien.danjou.info
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2011-03-07 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 13:43 Antoine Levitt
2011-03-07 14:42 ` Julien Danjou [this message]
2011-03-07 14:55 ` Antoine Levitt
2011-03-07 15:09 ` Julien Danjou
2011-03-07 18:52 ` Andreas Schwab
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=sa362rvxa9k.fsf@cigue.easter-eggs.fr \
--to=julien@danjou.info \
--cc=antoine.levitt@gmail.com \
--cc=ding@gnus.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).