From: Justin Guyett <justin@soze.net>
To: Chris Wedgwood <cw@f00f.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Jeff V. Merkey" <jmerkey@vger.timpanogas.org>,
<linux-kernel@vger.kernel.org>, <jmerkey@timpanogas.org>
Subject: Re: NWFS Submitted to Alan Cox
Date: Sun, 1 Jul 2001 12:23:17 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0107011220090.27557-100000@gw.soze.net> (raw)
In-Reply-To: <20010702025418.B14068@weta.f00f.org>
On Mon, 2 Jul 2001, Chris Wedgwood wrote:
> On Sun, Jul 01, 2001 at 01:50:00PM +0100, Alan Cox wrote:
>
> > I'm not a file sustem hacker, nor since I work for one vendor the
> > appropriate owner for larg chunks of code in some people's eyes. I
> > suspect the FSF is a much much better asignee for the code itself
>
> I assume the legal threats that Jeff has experience will follow the
> code? Surely before anyone wishes to adopt such a thing they should
> get legal advice about the situation?
>
> It would be shame to let potentially useful code be left to die for
> fear of bully-tactics if their claims are unfounded.
presuming they are unfounded, given the history of attacks by Novell,
perhaps the best move would be to turn it over to a company like compaq or
ibm given a written contract that they will keep it open source. Novell
can't be that stupid.
justin
next prev parent reply other threads:[~2001-07-01 19:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-01 0:35 NWFS Submitted to Alan Cox Jeff V. Merkey
2001-07-01 1:12 ` Jeff V. Merkey
2001-07-01 3:59 ` Paul Fulghum
2001-07-01 10:34 ` Jeff V. Merkey
2001-07-01 4:16 ` Trever L. Adams
2001-07-01 10:32 ` Jeff V. Merkey
2001-07-01 12:50 ` Alan Cox
2001-07-01 14:54 ` Chris Wedgwood
2001-07-01 19:23 ` Justin Guyett [this message]
2001-07-02 0:45 ` Jeff V. Merkey
2001-07-01 20:18 ` Jeff V. Merkey
2001-07-01 20:16 ` Jeff V. Merkey
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=Pine.LNX.4.33.0107011220090.27557-100000@gw.soze.net \
--to=justin@soze.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cw@f00f.org \
--cc=jmerkey@timpanogas.org \
--cc=jmerkey@vger.timpanogas.org \
--cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).