From: Michael Ellerman <mpe@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
gwshan@linux.vnet.ibm.com
Subject: Rebase of my fixes branch
Date: Mon, 15 Feb 2016 21:38:00 +1100 [thread overview]
Message-ID: <1455532680.26205.8.camel@ellerman.id.au> (raw)
Hi folks,
FYI I've rebased my fixes branch.
Unfortunately we had a couple of fixes in fixes that needed fixes in order to
be actual fixes.
So if you're basing some work on it you'll have to fetch and rebase.
The old head commit was: 0fe53e8d335bfc02f81300b70211e61fb931a725
and now it's: c777e2a8b65420b31dac28a453e35be984f5808b
cheers
next reply other threads:[~2016-02-15 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 10:38 Michael Ellerman [this message]
2016-02-15 11:16 ` Rebase of my fixes branch Aneesh Kumar K.V
2016-02-16 2:45 ` Michael Ellerman
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=1455532680.26205.8.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.