From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net,
sensors@stimpy.netroedge.com
Subject: Re: kernel maintainer's HOWTO for quilt and -mm
Date: Thu, 28 Apr 2005 16:47:08 -0700 [thread overview]
Message-ID: <20050428234708.GA23714@kroah.com> (raw)
In-Reply-To: <20050428163121.1343aa6c.akpm@osdl.org>
On Thu, Apr 28, 2005 at 04:31:21PM -0700, Andrew Morton wrote:
> Greg KH <greg@kroah.com> wrote:
> >
> > On Thu, Apr 28, 2005 at 03:34:14PM -0700, Greg KH wrote:
> > > Examples of the output of this script can be seen at:
> > > http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/
> >
> > Andrew, I'm now putting my broken out patches in this directory so you
> > can apply them to the -mm tree. You can take them in the 4 big chunks
> > (they all apply one after each other), or you can take the individual
> > patches if you want too (they also apply, one after each other.) It's
> > up to you what is easier for you to handle.
> >
> > Does this work out for you?
>
> Yes, it does. I'm now sucking
>
> gregkh-01-driver
> gregkh-02-i2c
> gregkh-03-pci
> gregkh-04-USB
> cpufreq
> agp
> alsa
>
> as individual patches and
>
> linus.patch
> git-ia64.patch
> git-net.patch
> git-scsi-misc.patch
> git-scsi-rc-fixes.patch
>
> from git repos.
>
> It's a bit of a hassle that your patches aren't based on latest -linus.
I understand. That will change, once the -git nightly snapshots start
up.
thanks,
greg k-h
next prev parent reply other threads:[~2005-04-28 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 22:34 Greg KH
2005-04-28 22:36 ` Greg KH
2005-04-28 23:31 ` Andrew Morton
2005-04-28 23:47 ` Greg KH [this message]
2005-04-29 0:07 ` 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=20050428234708.GA23714@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=sensors@stimpy.netroedge.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
all inboxes | Powered by JetHome®