From: Neil Jerram <neil@ossau.uklinux.net>
Cc: bug-guile@gnu.org
Subject: Re: [PATCH] posix.texi: added additional examples
Date: 19 Mar 2002 19:45:57 +0000 [thread overview]
Message-ID: <m3lmcoibnu.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <3C967532.6090806@kaidea.freeserve.co.uk>
>>>>> "Ian" == Ian Sheldon <is+guile@kaidea.freeserve.co.uk> writes:
Ian> No problems. Here's the patch without the extra @node
Ian> updates.
Many thanks.
Ian> I haven't signed any papers with the FSF so if the patch is considered
Ian> too big to incorporate without signing copyright papers then I'd be
Ian> happy to.
I don't know. It's not huge, but it is rather longer than the `about
10 lines' guideline that I've heard mentioned before.
Marius, can you advise?
Neil
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2002-03-19 19:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 17:55 [PATCH] posix.texi: added additional examples Ian Sheldon
2002-03-18 20:39 ` Neil Jerram
2002-03-18 23:16 ` Ian Sheldon
2002-03-19 19:45 ` Neil Jerram [this message]
2002-04-02 1:14 ` Rob Browning
2002-04-03 18:29 ` Marius Vollmer
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=m3lmcoibnu.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--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).