From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: bug-guile@gnu.org
Subject: Re: [PATCH] Fix bug: Init auto var to unrandomize `stack_depth' rv.
Date: Sun, 10 Jan 2010 18:41:36 +0100 [thread overview]
Message-ID: <87skadrh67.fsf@ambire.localdomain> (raw)
In-Reply-To: <m3k4vqrjxt.fsf@pobox.com> (Andy Wingo's message of "Sat, 09 Jan 2010 23:29:34 +0100")
() Andy Wingo <wingo@pobox.com>
() Sat, 09 Jan 2010 23:29:34 +0100
Applied, along with some other patches.
Cool, thanks.
If you're going to send patches like this, I'm very happy to
apply them; but it would be easier for me if you just sent the
messages produced by git-format-patch, so I could just pipe
your whole message through git-am.
As it is I have to edit the commit logs to cut until the
git-format-patch body.
Often i include some kind of commentary describing the patch or
the motivation of the patch, etc. Where should i include that
info? Maybe "git-format-patch --attach"?
thi
next prev parent reply other threads:[~2010-01-10 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 10:01 [PATCH] Fix bug: Init auto var to unrandomize `stack_depth' rv Thien-Thi Nguyen
2010-01-09 22:29 ` Andy Wingo
2010-01-10 17:41 ` Thien-Thi Nguyen [this message]
2010-01-12 19:35 ` Andy Wingo
2010-01-13 10:02 ` Ludovic Courtès
2010-01-13 13:56 ` Thien-Thi Nguyen
-- strict thread matches above, loose matches on Subject: below --
2010-01-09 8:28 Thien-Thi Nguyen
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87skadrh67.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=bug-guile@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 read-only IMAP folder(s) and NNTP newsgroup(s).