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: Can you include a new git tree in linux-next, the staging-next tree?
Date: Mon, 26 Apr 2010 17:01:04 -0700 [thread overview]
Message-ID: <20100427000104.GA31358@kroah.com> (raw)
Hi,
Welcome back from your break :)
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.
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.
If I've messed anything up, please let me know.
thanks,
greg k-h
next reply other threads:[~2010-04-27 0:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 0:01 Greg KH [this message]
2010-04-27 3:19 ` Can you include a new git tree in linux-next, the staging-next tree? Stephen Rothwell
2010-04-27 3:37 ` 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=20100427000104.GA31358@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