From: Holger Schurig <h.schurig@mn-logistik.de>
To: David Woodhouse <dwmw2@infradead.org>, linux-mtd@lists.infradead.org
Subject: Re: Porting FFS2 on MIPS
Date: Mon, 23 Jul 2001 17:29:32 +0200 [thread overview]
Message-ID: <20010723152933.2687DF445@lin01.mn-logistik.de> (raw)
In-Reply-To: <9387.995894275@redhat.com>
> The source to WinCE is now available, isn't it? Can you glean some
> information about FFS2 from there?
BEWARE !
The following is an assumption, not a known fact. And I am not a
lawyer, so your mileage may vary.
When you look into the source code of WinCE then you might at some time
experience the virus-like aspects of "shared source". Whenever you do
something in the same realm, it might be the case that someone is
trying to sue you because of "theft of industry secrets" or something
like this.
Such a situation could arise when Microsoft makes less and less revenue
and tries to use lawsuits instead of innovation to gain (or not loose)
market share. For them fighting even a bogus lawsuit is cheap, they pay
it from penny cash. But for a private person, trying to enhance Linux
for fun?
prev parent reply other threads:[~2001-07-23 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 13:19 Porting FFS2 on MIPS Raghav P
2001-07-23 13:17 ` David Woodhouse
2001-07-23 15:29 ` Holger Schurig [this message]
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=20010723152933.2687DF445@lin01.mn-logistik.de \
--to=h.schurig@mn-logistik.de \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.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