From: Andy Wingo <wingo@pobox.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Miscellaneous for 2.0
Date: Tue, 08 Mar 2011 23:46:34 +0100 [thread overview]
Message-ID: <m3k4g98c39.fsf@unquote.localdomain> (raw)
In-Reply-To: <87mxlesmbb.fsf@netris.org> (Mark H. Weaver's message of "Tue, 01 Mar 2011 13:55:04 -0500")
On Tue 01 Mar 2011 19:55, Mark H Weaver <mhw@netris.org> writes:
> I'd like to apply these to both stable-2.0 and master. Any
> objections?
Go ahead, and feel free to push trivial patches like this to
stable-2.0. They'll land on master as we merge stable-2.0 back there.
Thanks!
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-03-08 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 18:55 [PATCH] Miscellaneous for 2.0 Mark H Weaver
2011-03-08 22:46 ` Andy Wingo [this message]
[not found] <09.78.00574.7187E6D4@mx15>
2011-03-07 10:41 ` Daniel Llorens
[not found] <941810.39891.qm@web114116.mail.gq1.yahoo.com>
2011-02-14 20:39 ` Andy Wingo
2011-02-14 22:02 ` Mark H Weaver
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=m3k4g98c39.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.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).