From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [Q] Which tree should we work agains?
Date: Tue, 10 Jun 2014 11:16:34 +0000 [thread overview]
Message-ID: <20140610111634.GJ5015@mwanda> (raw)
In-Reply-To: <006601cf8478$52fb3310$f8f19930$@gmail.com>
On Tue, Jun 10, 2014 at 11:29:55AM +0200, Sima Baymani wrote:
> The patch you responded to in that link was aimed for staging. Previously,
> I have understood that staging work is done on staging-next - has this
> changed?
linux-next is compiled each day from staging-next and 100+ other devel
trees. It might be up to 24 hours behind staging-next but it's
basically the same thing.
regards,
dan carpenter
next prev parent reply other threads:[~2014-06-10 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 6:50 [Q] Which tree should we work agains? Yi Li
2014-06-10 8:06 ` Dan Carpenter
2014-06-10 11:16 ` Dan Carpenter [this message]
2014-06-10 12:22 ` Sima Baymani
2014-06-10 17:39 ` Yi Li
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=20140610111634.GJ5015@mwanda \
--to=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.