From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus <torvalds@linux-foundation.org>
Subject: Re: linux-next: Requirements and process
Date: Mon, 5 May 2008 21:48:46 -0700 [thread overview]
Message-ID: <20080506044846.GE4773@kroah.com> (raw)
In-Reply-To: <20080503154542.18807e59.sfr@canb.auug.org.au>
On Sat, May 03, 2008 at 03:45:42PM +1000, Stephen Rothwell wrote:
> I currently have 54 trees that (I assume) are of type 2 above:
>
> driver-core usb
Internally I have both of these trees split into "current" and "next"
sections, so that I know what to merge when.
If it would make things easier for you, I'd be glad to split both of
these trees up in such a manner to make it more visable.
Perhaps:
driver-core-next
usb-next
driver-core
usb
would be sufficient for you?
> And three trees that I am not sure about:
>
> x86-latest sched-latest ldp
ldp you have properly named as something that will probably go into
next-next or most likely next-next-next, but does build and run properly
today, yet has work to go in the "must clean up this crap" arena.
thanks,
greg k-h
prev parent reply other threads:[~2008-05-06 4:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 5:45 linux-next: Requirements and process Stephen Rothwell
2008-05-03 6:07 ` Stephen Rothwell
2008-07-22 22:31 ` Randy Dunlap
2008-07-23 4:28 ` Stephen Rothwell
2008-05-03 6:35 ` Andrew Morton
2008-05-03 7:45 ` Stephen Rothwell
2008-05-03 14:27 ` Andrew Morton
2008-07-23 4:41 ` Stephen Rothwell
2008-05-06 4:48 ` Greg KH [this message]
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=20080506044846.GE4773@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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