From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Jonathan Larmour <jifl@ecoscentric.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: Pros and cons of FSF
Date: Thu, 03 Apr 2003 08:29:00 -0000 [thread overview]
Message-ID: <20030403082554.GB19888@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <3E8BB24E.7080107@eCosCentric.com>
Hi Jifl
Many of the cons seem negotiable with FSF, depending on host strict
they are. Could you form a list of questions and see what they say?
Andrew
next prev parent reply other threads:[~2003-04-03 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 4:02 Jonathan Larmour
2003-04-03 8:29 ` Andrew Lunn [this message]
2003-04-03 13:40 ` Jonathan Larmour
2003-04-03 13:53 ` Gary Thomas
2003-04-03 13:55 ` Mark Salter
2003-04-03 17:12 ` Nick Garnett
2003-04-03 13:08 ` Mark Salter
2003-04-03 13:36 ` Jonathan Larmour
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030403082554.GB19888@biferten.ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@sources.redhat.com \
--cc=jifl@ecoscentric.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).