public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Hubert Mantel <mantel@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: UnitedLinux violating GPL?
Date: Mon, 13 Jan 2003 13:12:42 +0000	[thread overview]
Message-ID: <20030113131242.GF9031@codemonkey.org.uk> (raw)
In-Reply-To: <1042390241.15051.4.camel@irongate.swansea.linux.org.uk>

On Sun, Jan 12, 2003 at 04:50:43PM +0000, Alan Cox wrote:

 > > So you are saying that Alan Cox is violating the GPL since he releases his 
 > > -ac kernels only as one single monolithic patch against the vanilla tree, 
 > > not as individual patches (like Andrea Arcangeli does for example)?
 > > I think the motivation for this ridiculous thread is very obvious.
 > 
 > I think Dave needs to type "man diff" 8)

I think Dave needs a diff that allows me to keep as many patches
in sync as bk lets me.  We don't all have your superhuman
patch-fu Alan 8-)

I do periodic GNU diffs of the 'big bundle o' patches'.
There are even split up versions of the patches.
All there to see at k.o
The merges Ive done with bitkeeper to Linus recently
have been diffs already posted to the 2.4 commit list.
Asides from the AGP bits, which were 99% already posted
to linux-kernel. The remainder were trivial things, and they
showed up in -bk an hour or so later anyways..

		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2003-01-13 13:06 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09 22:27 UnitedLinux violating GPL? Jeff Garzik
2003-01-09 22:45 ` Philip Dodd
2003-01-10  0:27   ` Adrian Bunk
2003-01-10  0:36     ` Cort Dougan
2003-01-10  2:40   ` John Jasen
2003-01-10  2:47     ` Jeff Garzik
2003-01-10 19:05       ` Samuel Flory
2003-01-09 22:53 ` Cort Dougan
2003-01-09 23:00 ` Tom Sightler
2003-01-09 23:06 ` GertJan Spoelman
2003-01-09 23:19 ` Lars Marowsky-Bree
2003-01-09 23:23   ` Jeff Garzik
2003-01-10 10:38     ` Pavel Machek
2003-01-17 20:12       ` Jeff Garzik
2003-01-09 23:45 ` Jeff V. Merkey
2003-01-09 22:46   ` Jeff Garzik
2003-01-10  1:22     ` Jeff V. Merkey
2003-01-10  0:31   ` Aaron T Porter
2003-01-10  8:34 ` Hubert Mantel
2003-01-10 10:46   ` Henning P. Schmiedehausen
2003-01-11 10:52     ` Christoph Hellwig
2003-01-10 10:55 ` Horst von Brand
2003-01-10 12:19   ` Adrian Bunk
2003-01-11 16:34     ` Horst von Brand
2003-01-11 19:27       ` David Woodhouse
2003-01-12 13:15         ` Hubert Mantel
2003-01-12 16:50           ` Alan Cox
2003-01-13 13:12             ` Dave Jones [this message]
2003-01-12 13:23         ` Horst von Brand
2003-01-11 10:50 ` Christoph Hellwig
2003-01-11 11:00   ` Andre Hedrick
2003-01-11 14:46   ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2003-01-10 12:25 Nicholas Berry
     [not found] <20030109224013$6e5e@gated-at.bofh.it>
     [not found] ` <20030111110011$3252@gated-at.bofh.it>
2003-01-11 11:51   ` Andi Kleen
2003-01-11 14:28     ` Christoph Hellwig
2003-01-11 14:44       ` Andi Kleen
2003-01-11 20:34 Protasevich, Natalie

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=20030113131242.GF9031@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mantel@suse.de \
    /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