From: Boaz Harrosh <bharrosh@panasas.com>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.2-rc1
Date: Mon, 21 Nov 2011 17:41:01 -0800 [thread overview]
Message-ID: <4ECAFDAD.5040801@panasas.com> (raw)
In-Reply-To: <CA+5PVA6tBx4i1XZ+AF=uaOsjYCshG9CzXHWjnJcsJ=z1qw1F4A@mail.gmail.com>
On 11/09/2011 09:28 AM, Josh Boyer wrote:
>
> Fedora uses those. We also used the -gitX snapshot patches when they
> were generated, but now we do that by hand (which we also did for the
> -rcX patches while kernel.org was down.)
>
> josh
My god that totally-brain-dead Fedora Kernel rpm generation.
RANT a head should be skipped!!
I wish there was a strait forward way to point to a Kernel
git tree HEAD and say "make rpm", which is simply the tar
of the "make modules_install" and the "make install" output
+ a simple script to manipulate grub.conf
Not today's Fedora-Kernel git tree which is not a Linux
git tree at all but those patches above + stable.
Any simple tree moments needs to involve black patch magic
and fear of hell. (Don't try this at home)
Actually the "grub-selector" should have been it's own
rpm. And each Kernel can/should be it's own independent
(none conflicting, right) package. I know, I know, it tries
to be that, but it is not. For example I want a low-latency
rt Kernel as a side choice for any Kernel, and so on...
Throw away that monstrous Fedora-Kernel-tree. There is
only one Kernel tree it is called Linux. You can do your
own back/forward port branches based on stable to your
heart's content with out inventing a new totally different
patches tree.
Someone stop me. There is no end to the RANT I can
generate about Fedora Kernel release
Boaz
next prev parent reply other threads:[~2011-11-22 1:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 2:10 Linux 3.2-rc1 Linus Torvalds
2011-11-08 3:12 ` Al Viro
2011-11-08 4:26 ` Linus Torvalds
2011-11-08 10:52 ` Geert Uytterhoeven
2011-11-08 6:50 ` Nicholas A. Bellinger
2011-11-08 13:43 ` Udo Steinberg
2011-11-08 14:47 ` Ming Lei
2011-11-08 22:10 ` Rafael J. Wysocki
2011-11-08 14:53 ` Alessandro Suardi
2011-11-08 20:13 ` Linus Torvalds
2011-11-08 20:15 ` Matthew Garrett
2011-11-08 20:44 ` Linus Torvalds
2011-11-08 14:55 ` Nick Bowler
2011-11-08 20:23 ` Linus Torvalds
2011-11-09 7:40 ` Takashi Iwai
2011-11-09 7:40 ` Takashi Iwai
2011-11-09 12:03 ` Wu Fengguang
2011-11-10 11:57 ` Wu Fengguang
2011-11-10 11:57 ` Wu Fengguang
2011-11-08 19:06 ` Thomas Bächler
2011-11-08 23:00 ` Steven Rostedt
2011-11-08 23:53 ` Linus Torvalds
2011-11-09 8:09 ` Borislav Petkov
2011-11-09 13:11 ` Valdis.Kletnieks
2011-11-09 14:20 ` Paul Rolland
2011-11-09 23:23 ` Linus Torvalds
2011-11-09 17:18 ` Randy Dunlap
2011-11-09 17:28 ` Josh Boyer
2011-11-22 1:41 ` Boaz Harrosh [this message]
2011-11-22 16:10 ` Josh Boyer
2011-11-22 18:05 ` Alan Cox
2011-11-22 18:29 ` Boaz Harrosh
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=4ECAFDAD.5040801@panasas.com \
--to=bharrosh@panasas.com \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=torvalds@linux-foundation.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.