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: Tue, 25 Oct 2011 13:04:10 -0700 [thread overview]
Message-ID: <1319573050.6463.2.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <1319436327.15576.4.camel@haakon2.linux-iscsi.org>
On Sun, 2011-10-23 at 23:05 -0700, Nicholas A. Bellinger wrote:
> Hi Stephen,
>
> 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.
>
Hi Stephen,
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.
Thank you!
--nab
next prev parent reply other threads:[~2011-10-25 20:04 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 [this message]
2011-10-26 15:34 ` Stephen Rothwell
2011-10-26 19:44 ` Nicholas A. Bellinger
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=1319573050.6463.2.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=hch@lst.de \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=target-devel@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.