From: Klaus Schilling <schilling.klaus@web.de>
To: ludo@gnu.org
Cc: guile-devel@gnu.org
Subject: Re: Fmt Module
Date: Mon, 14 Mar 2011 18:35:50 +0100 (CET) [thread overview]
Message-ID: <20110314.183550.69381223.schilling.klaus@web.de> (raw)
In-Reply-To: <87oc5dtyfy.fsf@gnu.org>
From: ludo@gnu.org (Ludovic Courtès)
Subject: Re: Fmt Module
Date: Mon, 14 Mar 2011 18:16:17 +0100
>
> When we do include external libs, we should strive to leave upstream
> files unmodified, as is done for (sxml ssax), (system base lalr),
> (ice-9 match), and others.
Why does htmlprag not get included?
Klaus Schilling
next prev parent reply other threads:[~2011-03-14 17:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 21:14 Fmt Module Noah Lavine
2011-03-13 21:37 ` Andreas Rottmann
2011-03-14 3:54 ` Noah Lavine
2011-03-14 17:16 ` Ludovic Courtès
2011-03-14 17:35 ` Klaus Schilling [this message]
2011-03-27 11:07 ` Andy Wingo
2011-03-24 0:45 ` Andreas Rottmann
2011-03-24 21:14 ` Ludovic Courtès
2011-03-26 14:03 ` Andreas Rottmann
2011-03-27 14:01 ` Ludovic Courtès
2011-03-27 11:10 ` Andy Wingo
2011-03-27 15:38 ` Noah Lavine
2011-03-27 23:24 ` Andreas Rottmann
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=20110314.183550.69381223.schilling.klaus@web.de \
--to=schilling.klaus@web.de \
--cc=guile-devel@gnu.org \
--cc=ludo@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).