From: Antoine Levitt <antoine.levitt@gmail.com>
To: ding@gnus.org
Subject: Re: Inconsistent doc for message-generate-new-buffers
Date: Mon, 07 Mar 2011 15:55:50 +0100 [thread overview]
Message-ID: <87pqq3getl.fsf@gmail.com> (raw)
In-Reply-To: <sa362rvxa9k.fsf@cigue.easter-eggs.fr> (Julien Danjou's message of "Mon, 07 Mar 2011 15:42:15 +0100")
07/03/11 15:42, Julien Danjou
> On Mon, Mar 07 2011, Antoine Levitt wrote:
>
>> The info doc is out of date.
>
> Merged,
Thanks!
> but please include a ChangeLog entry next time, it'd be easier
> to merge.
Ah, right. I saw somebody talk about C-x 4 a and just tried it, it's
awesome. :) I'll do that next time.
> Git format-patch is welcome also. :)
It just seems too much trouble to maintain a separate branch, especially
since I tend to get extremely confused by git error messages and end up
doing a lot of git reset --hard :) So I just maintain a set a patches
without ever committing and I just do git stash && git pull && git stash
apply. It probably doesn't scale too well, but since my changes are
usually small enough not to require commits, that's good enough for me.
next prev parent reply other threads:[~2011-03-07 14:55 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
2011-03-07 14:55 ` Antoine Levitt [this message]
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=87pqq3getl.fsf@gmail.com \
--to=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).