All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, xfs@oss.sgi.com,
	David Chinner <david@fromorbit.com>,
	xfs-masters@oss.sgi.com
Subject: Re: XFS for-next branch
Date: Fri, 27 Jan 2012 10:01:37 -0600	[thread overview]
Message-ID: <20120127160137.GJ8262@sgi.com> (raw)
In-Reply-To: <20120127110533.10304c6a33b83ac8e778915c@canb.auug.org.au>

Hey Stephen,

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.

> Did you mean "3.3", or "3.4"?

I meant only that I'd like to try it this way for a single release, see
how it goes, and then re-evaluate.

> Currently the contacts for that tree are: David Chinner
> <david@fromorbit.com>, xfs-masters@oss.sgi.com.  Should I change that?
> i.e. who has control over the tree and can fix problems if I report them?

I think Dave's suggestion is reasonable:  Keep him as a contact, add me,
and s/xfs-masters@oss.sgi.com/xfs@oss.sgi.com/.  It really helps that
you two are in the same timezone.  ;)

Thanks,
	Ben

WARNING: multiple messages have this Message-ID (diff)
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: Fri, 27 Jan 2012 10:01:37 -0600	[thread overview]
Message-ID: <20120127160137.GJ8262@sgi.com> (raw)
In-Reply-To: <20120127110533.10304c6a33b83ac8e778915c@canb.auug.org.au>

Hey Stephen,

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.

> Did you mean "3.3", or "3.4"?

I meant only that I'd like to try it this way for a single release, see
how it goes, and then re-evaluate.

> Currently the contacts for that tree are: David Chinner
> <david@fromorbit.com>, xfs-masters@oss.sgi.com.  Should I change that?
> i.e. who has control over the tree and can fix problems if I report them?

I think Dave's suggestion is reasonable:  Keep him as a contact, add me,
and s/xfs-masters@oss.sgi.com/xfs@oss.sgi.com/.  It really helps that
you two are in the same timezone.  ;)

Thanks,
	Ben

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2012-01-27 16:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 17:12 XFS for-next branch Ben Myers
2012-01-25 17:12 ` Ben Myers
2012-01-27  0:05 ` Stephen Rothwell
2012-01-27  0:05   ` Stephen Rothwell
2012-01-27  0:26   ` Dave Chinner
2012-01-27 16:01   ` Ben Myers [this message]
2012-01-27 16:01     ` Ben Myers
2012-01-27 21:17     ` Stephen Rothwell
2012-01-27 21:17       ` Stephen Rothwell
2012-01-30 18:27       ` Ben Myers
2012-01-30 18:27         ` Ben Myers

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=20120127160137.GJ8262@sgi.com \
    --to=bpm@sgi.com \
    --cc=david@fromorbit.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 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.