From: Greg KH <gregkh@gentoo.org>
To: gentoo-kernel@lists.gentoo.org
Subject: Re: [gentoo-kernel] [ANNOUNCE] genpatches-2.6.15-9 release
Date: Wed, 1 Mar 2006 18:36:18 -0800 [thread overview]
Message-ID: <20060302023618.GA17128@kroah.com> (raw)
In-Reply-To: <44064CF6.2050709@gentoo.org>
On Thu, Mar 02, 2006 at 01:40:06AM +0000, Daniel Drake wrote:
> Daniel Drake wrote:
> >Revision 319:
> >Linux 2.6.15.5 (dsd)
> >Added: 1054_linux-2.6.15.5.patch
>
> I got lazy and just added the whole patch in one go. I haven't heard of
> any conflicts in a while so will probably continue to do it this way
> (much less effort) unless there are any complaints.
I would encourage you to do this, as you get the "extra" security
updates that were in the final release, but not in the list of review
patches.
thanks,
greg k-h
--
gentoo-kernel@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-02 2:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 1:30 [gentoo-kernel] [ANNOUNCE] genpatches-2.6.15-9 release Daniel Drake
2006-03-02 1:40 ` Daniel Drake
2006-03-02 2:36 ` Greg KH [this message]
2006-03-02 11:26 ` Daniel Drake
2006-03-02 16:43 ` Greg KH
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=20060302023618.GA17128@kroah.com \
--to=gregkh@gentoo.org \
--cc=gentoo-kernel@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox