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: Wed, 08 Oct 2008 05:57:37 +1100 [thread overview]
Message-ID: <1223405857.8157.55.camel@pasglop> (raw)
In-Reply-To: <9B078573-0862-4176-A945-E273D78B260F@kernel.crashing.org>
On Tue, 2008-10-07 at 07:29 -0500, Kumar Gala wrote:
> On Oct 7, 2008, at 12:27 AM, Benjamin Herrenschmidt wrote:
>
> > While paul was away, I've been taking care of the tree, so currently
> > up to date is my git at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc.git
> >
> > I've pushed a batch of stuff to the "master" branch. I haven't yet
> > updated the "next" branch, I'm going to let master settle a day or two
> > first just in case.
> >
> > I'll update patchwork status asap.
>
> Ben, remind me the difference between your 'master' and 'next'
> branches? Will you rebase 'master'?
Well, mostly they are the same, let's say that I'm trying to avoid
rebasing both, but if shit happens, it's better if master gets rebased
and not next though it's a bit arbitrary and Im not sure it's really
useful in practice.
Ben.
next prev parent reply other threads:[~2008-10-07 18:57 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 [this message]
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
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=1223405857.8157.55.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).