public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: Can you include a new git tree in linux-next, the staging-next tree?
Date: Mon, 26 Apr 2010 20:37:42 -0700	[thread overview]
Message-ID: <20100427033742.GA4759@kroah.com> (raw)
In-Reply-To: <20100427131935.9d48a17b.sfr@canb.auug.org.au>

On Tue, Apr 27, 2010 at 01:19:35PM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> On Mon, 26 Apr 2010 17:01:04 -0700 Greg KH <greg@kroah.com> wrote:
> >
> > Welcome back from your break :)
> 
> Thanks - I was nice and refreshed until about 9am this morning :-)
> 
> > Could you include a new git tree in linux-next, the staging-next tree
> > at:
> > 	git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-next-2.6.git
> > 
> > the branch is "staging-next" to pull from.
> 
> OK, I will add it at the end today.  I assume that this will be based off
> Linus' tree?

Yes.

> > I'm trying to do the -next work for staging in a git tree to keep my
> > development quilt trees smaller, and make it a bit easier for others to
> > work off of if they want to.
> 
> Should I drop the "staging" quilt tree?

Yes, but not the staging.current tree, I'll still use that for now in
quilt.

thanks,

greg k-h

      reply	other threads:[~2010-04-27  3:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27  0:01 Can you include a new git tree in linux-next, the staging-next tree? Greg KH
2010-04-27  3:19 ` Stephen Rothwell
2010-04-27  3:37   ` 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=20100427033742.GA4759@kroah.com \
    --to=greg@kroah.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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