linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: powerpc.git status
Date: Thu, 09 Oct 2008 06:16:45 +1100	[thread overview]
Message-ID: <1223493405.8157.76.camel@pasglop> (raw)
In-Reply-To: <9F5B82DA-D13D-4997-A247-59EAD0483230@kernel.crashing.org>

On Wed, 2008-10-08 at 07:10 -0500, Kumar Gala wrote:
> On Oct 8, 2008, at 4:29 AM, Benjamin Herrenschmidt wrote:
> 
> >
> >> Its useful to not rebase a branch you expect people to send you
> >> patches against and sub-maintainers are using to build tree's
> >> against.  It sounds like 'next' is that branch.
> >
> > Indeed. Though so far I've managed to avoid rebasing anything :-)
> 
> So what's the status of the patches moving from master into next?

Mostly "just in case". No big deal. I'll move them over today hopefully.

Ben.

  reply	other threads:[~2008-10-08 19:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07  5:27 powerpc.git status Benjamin Herrenschmidt
2008-10-07  8:38 ` [PATCH] powerpc/cell/oprofile: vma_map: fix test on overlay_tbl_offset Arnd Bergmann
2008-10-13 15:21   ` Robert Richter
2008-10-13 20:51     ` Benjamin Herrenschmidt
2008-10-07 12:29 ` powerpc.git status Kumar Gala
2008-10-07 18:57   ` Benjamin Herrenschmidt
2008-10-08  5:55     ` Kumar Gala
2008-10-08  9:29       ` Benjamin Herrenschmidt
2008-10-08 12:10         ` Kumar Gala
2008-10-08 19:16           ` Benjamin Herrenschmidt [this message]
2008-10-08 21:00             ` Kumar Gala

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=1223493405.8157.76.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=galak@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).