linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Updates to powerpc.git
Date: Sat, 12 Jul 2008 13:32:06 +1000	[thread overview]
Message-ID: <1215833526.7549.141.camel@pasglop> (raw)
In-Reply-To: <20080709091846.69b08e34@zod.rchland.ibm.com>

On Wed, 2008-07-09 at 09:18 -0400, Josh Boyer wrote:
> 
> If you want to use your master branch as a place for experimental
> stuff, that's fine by me.  But you'll want to keep next separate from
> it so it's as "clean" as possible for those trying to track what is
> definitely going into the next release.

Yes. The idea is that "next" stays clean.

> If it were up to me (which it's not), I would have master just track
> Linus, next track what's going into the next release, and "bleeding"
> or "experimental" track stuff that isn't fully vetted yet.  I might
> start doing that with my tree in the very near future.

Why keeping a branch to track linus in my public tree ? I have plenty of
these locally :-)

> Also, Paul is pretty good about not rebasing his branches when at all
> possible, and I suspect that's why his master and next were often the
> same.  It makes life lots easier for the sub-maintainers and anyone
> trying to track against the tree.  I humbly beg you to keep that
> going.

Yes. I intend to stay on that line, but as I'm new to the job, mistake
are more likely to happen.

Cheers,
Ben.

  parent reply	other threads:[~2008-07-12  3:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-09  7:34 Updates to powerpc.git Benjamin Herrenschmidt
2008-07-09 12:58 ` Kumar Gala
2008-07-09 16:08   ` Stephen Rothwell
2008-07-09 16:20     ` Grant Likely
2008-07-09 16:31       ` Josh Boyer
2008-07-09 16:47         ` Kumar Gala
2008-07-09 17:21           ` Josh Boyer
2008-07-09 17:25           ` Stephen Rothwell
2008-07-09 17:23       ` Stephen Rothwell
2008-07-09 17:30         ` Grant Likely
2008-07-12  3:30   ` Benjamin Herrenschmidt
2008-07-12  3:35     ` Grant Likely
2008-07-09 13:18 ` Josh Boyer
2008-07-09 13:40   ` Kumar Gala
2008-07-09 14:38     ` Grant Likely
2008-07-12  3:32   ` Benjamin Herrenschmidt [this message]
2008-07-14  5:32 ` Benjamin Herrenschmidt
2008-07-14  5:49   ` Stephen Rothwell
2008-07-14  8:37     ` Benjamin Herrenschmidt

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=1215833526.7549.141.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=akpm@linux-foundation.org \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.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 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).