From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ro0tSiEgE LKML <lkml@ro0tsiege.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: -ac kernels
Date: 15 Jul 2003 18:28:30 +0100 [thread overview]
Message-ID: <1058290104.3845.49.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <005b01c34aeb$e1c54e00$0500000a@bp>
On Maw, 2003-07-15 at 17:12, Ro0tSiEgE LKML wrote:
> What patches in the -ac kernels get put into the mainstream kernel? For
> instance, I would assume that fixes in 2.6.0-test1-ac1 would make it into
> 2.6.0-test2, but I'm not sure how that works, surely no one is just dropping
> those fixes and not applying them at some point to the mainline kernels. So
> I guess my question is, at what point does Linus' tree sync with Alan's?
I'm trying to hoover up patches that make things work so it can get more
people testing more and more driver stuff so that when Linus is back I
can nuke his mailbox from orbit...
next prev parent reply other threads:[~2003-07-15 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 16:12 -ac kernels Ro0tSiEgE LKML
2003-07-15 17:28 ` Alan Cox [this message]
2003-07-15 17:48 ` James Simmons
2003-07-15 17:50 ` Alan Cox
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=1058290104.3845.49.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@ro0tsiege.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;
as well as URLs for NNTP newsgroup(s).