From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: linux-powerpc "master" going to be rebased
Date: Wed, 07 Jan 2009 14:04:53 +1100 [thread overview]
Message-ID: <1231297493.14860.54.camel@pasglop> (raw)
Just a little warning...
I mistakenly did the same merge twice in "next" and "master" resulting
in those two branches now drifting for ever which they shouldn't.
I'm not going to rebase "next" as I pretty much promised, so I'm going
to rebase "master" to point to the same commit as "next".
I'll do that sometimes tomorrow.
Cheers,
Ben.
reply other threads:[~2009-01-07 3:04 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=1231297493.14860.54.camel@pasglop \
--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).