From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Chris Wedgwood <cw@f00f.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, jmerkey@timpanogas.org
Subject: Re: NWFS Submitted to Alan Cox
Date: Sun, 1 Jul 2001 13:18:26 -0700 [thread overview]
Message-ID: <20010701131826.B11188@vger.timpanogas.org> (raw)
In-Reply-To: <E15Ggfo-0004PN-00@the-village.bc.nu> <20010702025418.B14068@weta.f00f.org>
In-Reply-To: <20010702025418.B14068@weta.f00f.org>; from cw@f00f.org on Mon, Jul 02, 2001 at 02:54:18AM +1200
On Mon, Jul 02, 2001 at 02:54:18AM +1200, 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?
>
> I would also expect if the FSF are not the assignee (the suggest that
> they be is a very good one), then whomever does adopt it might want to
> make sure they have some kind of legal representation available should
> they need it.
>
> It would be shame to let potentially useful code be left to die for
> fear of bully-tactics if their claims are unfounded.
>
Their power only extends to the borders of this state. They have little
ability to interfere wth someone in Swansea, Great Britian, or even
Silicon Valley, California. The problem I have is they can get the
local courts here to do whatever they ask. Not so other places. I think
it's pretty safe so long as I am not the one releasing it.
Jeff
>
> --cw
next prev parent reply other threads:[~2001-07-01 21:31 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
2001-07-02 0:45 ` Jeff V. Merkey
2001-07-01 20:18 ` Jeff V. Merkey [this message]
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=20010701131826.B11188@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cw@f00f.org \
--cc=jmerkey@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).