From: Andy Wingo <wingo@pobox.com>
To: Mark Harig <idirectscm@aim.com>
Cc: bug-guile@gnu.org
Subject: Re: Missing and out-of-date information in guile.1, the Guile man page
Date: Sat, 05 Mar 2011 20:29:29 +0100 [thread overview]
Message-ID: <m3vczxcqna.fsf@unquote.localdomain> (raw)
In-Reply-To: <8CDA8E5BB95D253-584-D4A3@webmail-m087.sysops.aol.com> (Mark Harig's message of "Fri, 04 Mar 2011 19:45:18 -0500")
Hi Mark,
On Sat 05 Mar 2011 01:45, Mark Harig <idirectscm@aim.com> writes:
> On Fri, Mar 04, 2011 at 10:35:50AM +0100, Andy Wingo wrote:
>> On Tue 25 Jan 2011 08:05, Mark Harig <idirectscm@aim.com> writes:
>>
>> > On Mon, Jan 24, 2011 at 10:54:56PM +0100, Andy Wingo wrote:
>> >>
>> >> I updated the man page. I don't really know groff
>> >> though, so please reply with comments (text appended).
>> >>
>> >
>> > Thank you for the updated version.
>> >
>> > I have written a patch to this updated version. Please find
>> > it attached.
>>
>> Super, thanks!
>>
>> Can you attach it in git-format-patch format? That way when I apply
> it
>> we get your commit log and your name on the commit.
>>
>
> Done. Please find attached a plain-text patch file for
> doc/guile.1 generated from the command:
Applied. Thank you!
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-03-05 19:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 21:58 Missing and out-of-date information in guile.1, the Guile man page Mark Harig
2011-01-15 20:48 ` Neil Jerram
2011-01-16 19:38 ` Mark Harig
2011-01-19 19:50 ` Ken Raeburn
2011-01-20 2:31 ` Mark Harig
2011-01-24 21:07 ` Andy Wingo
2011-01-16 23:23 ` Mark Harig
2011-01-24 21:54 ` Andy Wingo
2011-01-25 7:05 ` Mark Harig
2011-03-04 9:35 ` Andy Wingo
[not found] ` <8CDA8E5BB95D253-584-D4A3@webmail-m087.sysops.aol.com>
2011-03-05 19:29 ` Andy Wingo [this message]
2011-01-24 21:06 ` Andy Wingo
2011-01-24 23:05 ` Mark Harig
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=m3vczxcqna.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=idirectscm@aim.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).