From: Ben Myers <bpm@sgi.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: xfs-masters@oss.sgi.com, linux-next@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS for-next branch
Date: Mon, 30 Jan 2012 12:27:17 -0600 [thread overview]
Message-ID: <20120130182717.GE7762@sgi.com> (raw)
In-Reply-To: <20120128081709.e7b0df733e5d35fe625eeea0@canb.auug.org.au>
Hi Stephen,
On Sat, Jan 28, 2012 at 08:17:09AM +1100, Stephen Rothwell wrote:
> On Fri, 27 Jan 2012 10:01:37 -0600 Ben Myers <bpm@sgi.com> wrote:
> >
> > On Fri, Jan 27, 2012 at 11:05:33AM +1100, Stephen Rothwell wrote:
> > > On Wed, 25 Jan 2012 11:12:44 -0600 Ben Myers <bpm@sgi.com> wrote:
> > > >
> > > > Could you pull XFS updates from
> > > >
> > > > git://oss.sgi.com/xfs/xfs.git for-next
> > > >
> > > > instead of from the oss/master branch for 3.3?
> > >
> > > OK, currently I fetch the "master" branch of that tree. And you want em
> > > to switch to the "for-next" branch, right? (Those two branches currently
> > > point to the same commit, so I have not changed yet.)
> >
> > Yep, please switch to oss/for-next instead of oss/master. I'll keep
> > them in sync normally, it's just that I'd like to have a little
> > flexability WRT what is in for-next.
>
> Just to be crystal clear: there are no branches in that tree called
> "oss/for-next" or "oss/master" - I assume that you are referring to the
> branches called "for-next" and "master", right?
I am referring to for-next and master branches, at
git://oss.sgi.com/xfs/xfs.git. Sorry I wasn't very clear.
Thanks,
Ben
prev parent reply other threads:[~2012-01-30 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 17:12 XFS for-next branch Ben Myers
2012-01-27 0:05 ` Stephen Rothwell
2012-01-27 0:26 ` Dave Chinner
2012-01-27 16:01 ` Ben Myers
2012-01-27 21:17 ` Stephen Rothwell
2012-01-30 18:27 ` Ben Myers [this message]
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=20120130182717.GE7762@sgi.com \
--to=bpm@sgi.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=xfs-masters@oss.sgi.com \
--cc=xfs@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).