linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev@ozlabs.org
Subject: Changes to my -next branch
Date: Tue, 17 Mar 2015 16:54:29 +1100	[thread overview]
Message-ID: <1426571669.4770.19.camel@kernel.crashing.org> (raw)

Hi folks !

My -next branch has been somewhat dormant lately. Now that we have that
new two-headed maintainership model, I'll change the way it works.

I'm going to merge patches in topic branches exclusively. One per series
and a next-misc for random other stuff.

"next" itself will just be an aggregate of these and will possibly be
rebased, nobody should work on top of next anyway. If you rely on some
work in any of the topic branches, pull *that*.

The topic branches themselves are meant to have the "don't rebase"
semantics, ie, if such a branch goes into my "nest", it means that
I intend to send it to Linus in my pull request (or via mpe) as-is. I
*might* drop the branch but that is a last-minute fuse thing that
I hope I don't have to use.

I'll start pushing things out tomorrow.

Cheers,
Ben.

                 reply	other threads:[~2015-03-17  5:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1426571669.4770.19.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --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).