From: "Nicholas A. Bellinger" <nab@linux-iscsi•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next <linux-next@vger•kernel.org>,
target-devel <target-devel@vger•kernel.org>,
Christoph Hellwig <hch@lst•de>
Subject: Re: Updated target-pending.git branches for linux-next
Date: Wed, 26 Oct 2011 12:44:01 -0700 [thread overview]
Message-ID: <1319658241.421.1.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <20111027023405.f4f5d5b24eb504119c59892c@canb.auug.org.au>
On Thu, 2011-10-27 at 02:34 +1100, Stephen Rothwell wrote:
> Hi Nicholas,
>
> On Tue, 25 Oct 2011 13:04:10 -0700 "Nicholas A. Bellinger" <nab@linux-iscsi•org> wrote:
> >
> > On Sun, 2011-10-23 at 23:05 -0700, Nicholas A. Bellinger wrote:
> > >
> > > The target-pending.git tree is now back on kernel.org, and as before
> > > the following branch is used as 'for-next' updates to existing
> > > drivers/target/ code:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git for-next
> > >
> > > I've also added another branch that is being used for new target modules
> > > being merged in the next development cycle:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git for-next-merge
> > >
> > > If you would be so kind, please go ahead and add the second entry as well
> > > into your linux-next daily builds.
> >
> > Just another friendly reminder to please add the for-next-merge branch
> > into Next/Trees.. Also if you would, please change the tree names to
> > 'target-updates' and 'target-merge' respectively.
>
> You said above that the for-next-merge branch is for "new target modules
> being merged in the next development cycle" which I assumed to mean that
> they would be intended for v3.3. As such, I will add that branch after
> v3.2-rc1 is released. Let me know if my assumption is incorrect.
>
Sorry, that is not what I intended to convey. What's currently in
for-next-merge it what's slated to go in this merge window.. Apologies
for the extra confusion.
> I have renamed iscsi-target to target-updates.
Thank you.
--nab
next prev parent reply other threads:[~2011-10-26 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 6:05 Updated target-pending.git branches for linux-next Nicholas A. Bellinger
2011-10-25 20:04 ` Nicholas A. Bellinger
2011-10-26 15:34 ` Stephen Rothwell
2011-10-26 19:44 ` Nicholas A. Bellinger [this message]
2011-10-27 15:09 ` Stephen Rothwell
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=1319658241.421.1.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi$(echo .)org \
--cc=hch@lst$(echo .)de \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=target-devel@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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