From: Gary Thomas <gary@mlbassoc.com>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: Andrew Lunn <andrew.lunn@ascom.ch>,
eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: Pros and cons of FSF
Date: Thu, 03 Apr 2003 13:53:00 -0000 [thread overview]
Message-ID: <1049377984.16212.12024.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <3E8C39C7.7030206@eCosCentric.com>
On Thu, 2003-04-03 at 06:40, Jonathan Larmour wrote:
> Andrew Lunn wrote:
> > 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?
>
> In fact, one of the purposes was to create this list so I could easily see
> what the questions were :-).
>
> Yes I can do it, but I'd like some buy-in that if the answers were all
> positive, this is something we would likely still want to pursue, given my
> summarising e-mail.
>
> So are others (Gary, Nick, Bart, John, Mark) definitely interested in
> pursuing this if the answers are positive?
Yes.
n.b. after seeing all of the bickering that goes on the SPI
mailing lists, I'm not so sure that could ever work anyway.
--
------------------------------------------------------------
Gary Thomas |
MLB Associates | Consulting for the
+1 (970) 229-1963 | Embedded world
http://www.mlbassoc.com/ |
email: <gary@mlbassoc.com> |
gpg: http://www.chez-thomas.org/gary/gpg_key.asc
------------------------------------------------------------
next prev parent reply other threads:[~2003-04-03 13:53 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
2003-04-03 13:40 ` Jonathan Larmour
2003-04-03 13:53 ` Gary Thomas [this message]
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=1049377984.16212.12024.camel@hermes.chez-thomas.org \
--to=gary@mlbassoc.com \
--cc=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).