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 00:39:07 +0100 [thread overview]
Message-ID: <20130317233907.GB4809@zurbaran> (raw)
In-Reply-To: <20130316132753.591db4c078d06db297ba46a8@canb.auug.org.au>
Hi Stephen,
On Sat, Mar 16, 2013 at 01:27:53PM +1100, Stephen Rothwell wrote:
> Hi Samuel,
>
> On Fri, 15 Mar 2013 17:46:25 +0100 Samuel Ortiz <sameo@linux.intel.com> wrote:
> >
> > On Thu, Mar 14, 2013 at 01:02:01AM +0100, Samuel Ortiz wrote:
> > >
> > > I am moving the MFD development from mfd-2.6.git/for-next to a new mfd-next
> > > tree:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/sameo/mfd-next.git
> > >
> > > Could you please point linux-next at it ? Many thanks in advance.
>
> Done.
Thanks.
> 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'm also carrying MFD fixes through the mfd-fixes tree:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/sameo/mfd-fixes.git
> >
> > Could you please also add it to linux-next ?
>
> 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.
> BTW, those two trees look very similar (in fact "diff -u <(git ls-remote
> mfd) <(git ls-remote mfd-fixes)" only shows a couple of differences in
> all the refs). You do realise that I can use 2 different branches of one
> tree, right (as can others)?
I understand that :) But using 2 trees rather than 2 separate branches is more
convenient to my personal workflow.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2013-03-17 23:39 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 [this message]
2013-03-17 23:45 ` Stephen Rothwell
2013-03-18 0:11 ` Samuel Ortiz
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=20130317233907.GB4809@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