From: Andy Wingo <wingo@pobox.com>
To: Douglas Mencken <dougmencken@gmail.com>
Cc: bug-guile@gnu.org
Subject: Re: [patches] three patches for configure.ac (and not only)
Date: Sat, 02 Apr 2011 15:55:35 +0200 [thread overview]
Message-ID: <m3vcywu59k.fsf@unquote.localdomain> (raw)
In-Reply-To: <AANLkTiktxPDjf9uySUhxas8jEtRNH9pWr-BWa+xCkEo1@mail.gmail.com> (Douglas Mencken's message of "Sat, 2 Apr 2011 15:40:15 +0200")
Hi Douglas,
I had said:
>> Can you re-post these patches as patches, please, using `diff -u', or
>> git-format-patch. Please include log messages as well.
You replied:
On Sat 02 Apr 2011 15:40, Douglas Mencken <dougmencken@gmail.com> writes:
> Build log if those patches are not applied is attached. Do you really
> prefer diff rather than sed? Okay. I can apply and diff then, if you
> do like diff so much and don't have `sed' on your side.
I prefer git-format-patch output :) By "log messages", I meant commit
log messages, not build logs.
Thanks,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2011-04-02 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 17:52 [patches] three patches for configure.ac (and not only) Douglas Mencken
2011-04-01 9:09 ` Andy Wingo
2011-04-02 13:40 ` Douglas Mencken
2011-04-02 13:55 ` Andy Wingo [this message]
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=m3vcywu59k.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=dougmencken@gmail.com \
/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).