From: Samuel Ortiz <sameo@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: New MFD tree for linux-next
Date: Mon, 18 Mar 2013 01:11:02 +0100 [thread overview]
Message-ID: <20130318001102.GC4809@zurbaran> (raw)
In-Reply-To: <20130318104520.06b6a22c577be324880a4d06@canb.auug.org.au>
On Mon, Mar 18, 2013 at 10:45:20AM +1100, Stephen Rothwell wrote:
> On Mon, 18 Mar 2013 00:39:07 +0100 Samuel Ortiz <sameo@linux.intel.com> wrote:
> >
> > > I assume that you are still using the for-next branch?
> > I will update for-next branch to be in sync with mfd-next until the 3.10 merge
> > window closes. After that I'll probably delete the mfd-2.6.git tree.
>
> I meant "I assume that I should still fetch the for-next branch
> of ...sameo/mfd-next.git". If that has changed, please let me know.
Sorry for the misunderstanding, I was not clear enough: mfd-next master is
replacing mfd-2.6 for-next and mfd-fixes master is replacing mfd-2.6 for-linus.
So no need to pull mfd-next for-next.
I deleted all branches but master from both mfd-next and mfd-fixes, so things
should be clearer now.
> > > What branch should I use of that?
> > Ah, I didn't see that the remote tree still carries the mfd-2.6 branches, I'll
> > remove them.
> > Please use master.
>
> OK. I will do that from tomorrow.
Thanks a lot.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2013-03-18 0:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 0:02 New MFD tree for linux-next Samuel Ortiz
2013-03-15 16:46 ` Samuel Ortiz
2013-03-16 2:27 ` Stephen Rothwell
2013-03-17 23:39 ` Samuel Ortiz
2013-03-17 23:45 ` Stephen Rothwell
2013-03-18 0:11 ` Samuel Ortiz [this message]
2013-03-18 0:13 ` 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=20130318001102.GC4809@zurbaran \
--to=sameo@linux.intel.com \
--cc=linux-kernel@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