From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: bug-guile@gnu.org
Subject: Re: [PATCH] Update configure script hints wrt precious env vars.
Date: Wed, 13 Jan 2010 21:35:02 +0100 [thread overview]
Message-ID: <87eilthhft.fsf@ambire.localdomain> (raw)
In-Reply-To: <m3ska9lr4n.fsf@pobox.com> (Andy Wingo's message of "Wed, 13 Jan 2010 20:52:08 +0100")
() Andy Wingo <wingo@pobox.com>
() Wed, 13 Jan 2010 20:52:08 +0100
I figured out how to use shell-command-on-region, M-|, so I
don't care any more about whether there's comments before or
after, though Ludovic is probably right about where they should
go. So submit as you like.
See also `gnus-summary-pipe-message'.
thi
next prev parent reply other threads:[~2010-01-13 20:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 13:49 [PATCH] Update configure script hints wrt precious env vars Thien-Thi Nguyen
2010-01-09 22:31 ` Andy Wingo
2010-01-10 17:37 ` Thien-Thi Nguyen
2010-01-12 19:34 ` Andy Wingo
2010-01-13 8:19 ` Thien-Thi Nguyen
2010-01-13 19:52 ` Andy Wingo
2010-01-13 20:35 ` Thien-Thi Nguyen [this message]
2010-01-13 21:06 ` Andy Wingo
2010-01-14 11:04 ` Thien-Thi Nguyen
2010-01-14 19:53 ` Andy Wingo
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=87eilthhft.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).