All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ben Collins <bcollins@ubuntu.com>, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Ubuntu kernel tree
Date: Mon, 07 Nov 2005 16:33:21 +0000	[thread overview]
Message-ID: <436F81D1.7000100@gentoo.org> (raw)
In-Reply-To: <1131316729.1212.58.camel@localhost.localdomain>

Alan Cox wrote:
> The FC kernel trees rpms and source rpms are distributed from the fedora
> site. 'Production' kernels go to the updates directory, others which are
> intended for testing go to the update testing directory and may or may
> not work wonderfully.

Source RPM's will just contain a Linux kernel tree with your patches already 
applied, right?

Is there an easier way to see what redhat/fedora have patched in, short of 
finding the closest vanilla tree and using "diff"?

Daniel

  reply	other threads:[~2005-11-07 16:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-06  1:37 [ANNOUNCE] Ubuntu kernel tree Ben Collins
2005-11-06 10:54 ` Jon Masters
2005-11-06 11:03 ` Rogério Brito
2005-11-06 14:48 ` Daniel Drake
2005-11-06 19:02   ` Jon Masters
2005-11-06 22:38   ` Alan Cox
2005-11-07 16:33     ` Daniel Drake [this message]
2005-11-07 17:08       ` Alan Cox
2005-11-07 17:05         ` Xavier Bestel
2005-11-07 17:23           ` Michael Alan Dorman
2005-11-07 17:32           ` Adrian Bunk
2005-11-09 14:09             ` Ben Collins
2005-11-06 20:26 ` Pavel Machek
2005-11-09 14:12   ` Ben Collins
2005-11-09 22:20     ` Greg KH
2005-11-06 20:36 ` Greg KH
2005-11-09 14:13   ` Ben Collins
  -- strict thread matches above, loose matches on Subject: below --
2005-11-07 16:44 Xose Vazquez Perez

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=436F81D1.7000100@gentoo.org \
    --to=dsd@gentoo.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bcollins@ubuntu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.