mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Weimer@CERT.Uni-Stuttgart.DE (Florian Weimer)
Cc: Torrey.Hoffman@myrio.com (Torrey Hoffman),
	jsimmons@transvirtual.com (James Simmons),
	linux-kernel@vger.kernel.org
Subject: Re: ReiserFS Bug Fixes 3 of 6 (Please apply all 6)
Date: Sat, 13 Apr 2002 21:03:35 +0100 (BST)	[thread overview]
Message-ID: <E16wTkF-000180-00@the-village.bc.nu> (raw)
In-Reply-To: <878z7vxmxz.fsf@CERT.Uni-Stuttgart.DE> from "Florian Weimer" at Apr 10, 2002 11:28:56 PM

> | binary form) with the major components (compiler, kernel, and so on)
> | of the operating system on which the executable runs, unless that
> | component itself accompanies the executable.
> 
> Modules for proprietary kernels seem to be okay, don't they?

It doesnt normally accompany the executable - thats an irrelevant ite,

> > Finally, that second option could be even more difficult... I hear 
> > MS has recently changed the terms of their C run-time-library license
> > to forbid use by GPLed code.
> 
> This is extremely unlikely, as Microsoft is selling its own version of
> an operation system with GNU components. ;-)

Microsoft are not required to obey their own licenses

  reply	other threads:[~2002-04-13 19:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-10 21:18 Torrey Hoffman
2002-04-10 21:28 ` Florian Weimer
2002-04-13 20:03   ` Alan Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-05 20:27 Hans Reiser
2002-04-05 21:48 ` Linus Torvalds
2002-04-06  1:10   ` Larry McVoy
2002-04-06 12:00     ` Hans Reiser
2002-04-06 17:01       ` Larry McVoy
2002-04-07 10:04         ` Hans Reiser
2002-04-10 19:21       ` Florian Weimer
2002-04-10 19:34         ` James Simmons
2002-04-10 19:55           ` Florian Weimer

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=E16wTkF-000180-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=Torrey.Hoffman@myrio.com \
    --cc=Weimer@CERT.Uni-Stuttgart.DE \
    --cc=jsimmons@transvirtual.com \
    --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

all inboxes | Powered by JetHome®