From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Greg KH <greg@kroah.com>, Jeff Garzik <jeff@garzik.org>,
wireless <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Theodore Tso <tytso@mit.edu>
Subject: Re: Elaboration on "Equivalent fix must already exist in Linus' tree"
Date: Tue, 03 Mar 2009 19:13:53 +0100 [thread overview]
Message-ID: <49AD7361.308@s5r6.in-berlin.de> (raw)
In-Reply-To: <43e72e890903030923v27c47f5anc184c0e8085bc5c1@mail.gmail.com>
Luis R. Rodriguez wrote:
> On Tue, Mar 3, 2009 at 7:27 AM, Stefan Richter
> <stefanr@s5r6.in-berlin.de> wrote:
>> Luis R. Rodriguez wrote:
>>> OK small silly example is convincing distributions it may be a good
>>> idea to carry linux-next kernel packages as options to users to
>>> hopefully down the road reduce the delta between what they carry and
>>> what is actually upstream.
>> Distros would do their users a bigger favour if [...]
>
> I don't think I was very clear in what I meant about "carrying
> linux-next kernel packages as an option". What I meant was carrying it
> just as an option for those users who want to test bleeding edge
> without compiling their own linux-next, _not_ to merge linux-next
> things into their own default kernel release and shove it down users
> throats.
Sorry, I meant "bigger favour" relative to carrying an own delta of
considerable size.
Packaging linux-next would be fine if the workload isn't a problem for
the packager. As pointed out elsewhere, there are caveats with
linux-next (e.g. a functionality which was in it yesterday could be gone
today because of a merge issue), but that's the nature of bleeding edge
of course.
--
Stefan Richter
-=====-==--= --== ---==
http://arcgraph.de/sr/
next prev parent reply other threads:[~2009-03-03 18:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 5:43 Elaboration on "Equivalent fix must already exist in Linus' tree" Luis R. Rodriguez
2009-03-03 5:57 ` Jeff Garzik
2009-03-03 6:44 ` Luis R. Rodriguez
2009-03-03 7:20 ` Jeff Garzik
2009-03-03 7:26 ` Greg KH
2009-03-03 7:37 ` Luis R. Rodriguez
2009-03-03 7:42 ` david
2009-03-03 7:57 ` Luis R. Rodriguez
2009-03-03 9:16 ` Theodore Tso
2009-03-03 15:19 ` Stefan Richter
2009-03-03 14:53 ` Greg KH
2009-03-03 15:27 ` Stefan Richter
2009-03-03 17:23 ` Luis R. Rodriguez
2009-03-03 18:13 ` Stefan Richter [this message]
2009-03-03 18:43 ` Luis R. Rodriguez
2009-03-03 22:55 ` david
2009-03-03 6:27 ` Greg KH
2009-03-03 14:43 ` John W. Linville
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=49AD7361.308@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=greg@kroah.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).