From: Marc Koschewski <marc@osknowledge.org>
To: Paul Jackson <pj@sgi.com>
Cc: "Martin J. Bligh" <mbligh@mbligh.org>,
marc@osknowledge.org, dtor_core@ameritech.net,
rlrevell@joe-job.com, 76306.1226@compuserve.com, akpm@osdl.org,
linux-kernel@vger.kernel.org, rdunlap@xenotime.net
Subject: Re: Wanted: hotfixes for -mm kernels
Date: Sun, 5 Feb 2006 09:58:34 +0100 [thread overview]
Message-ID: <20060205085833.GB5663@stiffy.osknowledge.org> (raw)
In-Reply-To: <20060204185646.f8e4e53e.pj@sgi.com>
* Paul Jackson <pj@sgi.com> [2006-02-04 18:56:46 -0800]:
> Do we need a place to put hotfix patches, or do we just need a list of
> links to lkml postings to said patches. Such a list has the advantage
> of pointing into the discussion surrounding each such fix, and such a
> list has the advantage of not holding so much redundant data (these
> patches will be redundant with what was posted on lkml). Redundant
> data out of context goes stale, and is less valuable.
>
> I can imagine someone (not me ;) keeping a wiki web page, listing for
> each *-mm and Linus release the particular lkml patch postings that one
> needs to pick off to get a build and boot.
>
> Just brainstorming ...
That would just come closer to a repositories check-in description. I vote for
such a thing. If it is a wiki or not.
Marc
next prev parent reply other threads:[~2006-02-05 8:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 20:00 Chuck Ebbert
2006-02-02 20:53 ` Lee Revell
2006-02-02 21:45 ` Dmitry Torokhov
2006-02-02 21:48 ` Randy.Dunlap
2006-02-02 21:57 ` Dmitry Torokhov
2006-02-03 10:07 ` Marc Koschewski
2006-02-04 16:37 ` Martin J. Bligh
2006-02-04 18:57 ` Marc Koschewski
2006-02-04 19:22 ` Martin J. Bligh
2006-02-05 8:56 ` Marc Koschewski
2006-02-04 20:41 ` Adrian Bunk
2006-02-05 9:09 ` Marc Koschewski
2006-02-05 15:13 ` Adrian Bunk
2006-02-05 2:56 ` Paul Jackson
2006-02-05 8:58 ` Marc Koschewski [this message]
2006-02-05 15:58 ` Martin J. Bligh
2006-02-05 17:15 ` Paul Jackson
2006-02-02 22:08 Chuck Ebbert
2006-02-02 22:29 ` Andrew Morton
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=20060205085833.GB5663@stiffy.osknowledge.org \
--to=marc@osknowledge.org \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.org \
--cc=pj@sgi.com \
--cc=rdunlap@xenotime.net \
--cc=rlrevell@joe-job.com \
/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
Powered by JetHome