[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-ppc] [Qemu-devel] [PULL 0/4] ppc patches for qemu-2.7 stable b
From: |
David Gibson |
Subject: |
Re: [Qemu-ppc] [Qemu-devel] [PULL 0/4] ppc patches for qemu-2.7 stable branch |
Date: |
Fri, 14 Oct 2016 09:28:35 +1100 |
User-agent: |
Mutt/1.7.0 (2016-08-17) |
On Thu, Oct 13, 2016 at 12:57:19PM +0100, Peter Maydell wrote:
> On 13 October 2016 at 12:54, Peter Maydell <address@hidden> wrote:
> > On 13 October 2016 at 06:15, David Gibson <address@hidden> wrote:
> >> The following changes since commit
> >> 1dc33ed90bf1fe1c2014dffa0d9e863c520d953a:
> >>
> >> Update version for v2.7.0 release (2016-09-02 13:44:11 +0100)
> >>
> >> are available in the git repository at:
> >>
> >> git://github.com/dgibson/qemu.git tags/ppc-for-2.7-20161013
> >>
> >> for you to fetch changes up to 2e68f28854f0120c9a938a61b64aaf1eaecb162b:
> >>
> >> ppc: Check the availability of transactional memory (2016-10-13 12:58:06
> >> +1100)
> >
> > Applied to master, thanks. (I hope that was what you had in mind;
> > if not we'll have to unwind stuff somehow...)
>
> unwind> looking more closely, there's no actual diff between HEAD
> now and what it was, so the merge commit is a no-op of sorts.
> Hopefully it doesn't cause any problems.
Right.. these were all (clean) cherry picks from the master branch
anyway, so I'd expect it to be a no-op.
> More generally, we need to come up with something for distinguishing
> PULL requests not for master, because my current workflow basically
> says "anything that says 'for you to fetch changes up to' will get
> merged into master...
Um.. yes.. this was intended for merge to the 2.7 branch, not master.
Any ideas how I should express that?
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
signature.asc
Description: PGP signature
- [Qemu-ppc] [PULL 0/4] ppc patches for qemu-2.7 stable branch, David Gibson, 2016/10/13
- [Qemu-ppc] [PULL 2/4] hw/ppc/spapr: Move code related to "ibm, pa-features" to a separate function, David Gibson, 2016/10/13
- [Qemu-ppc] [PULL 4/4] ppc: Check the availability of transactional memory, David Gibson, 2016/10/13
- [Qemu-ppc] [PULL 1/4] linux-headers: update, David Gibson, 2016/10/13
- [Qemu-ppc] [PULL 3/4] hw/ppc/spapr: Fix the selection of the processor features, David Gibson, 2016/10/13
- Re: [Qemu-ppc] [Qemu-devel] [PULL 0/4] ppc patches for qemu-2.7 stable branch, Peter Maydell, 2016/10/13
- Re: [Qemu-ppc] [Qemu-devel] [PULL 0/4] ppc patches for qemu-2.7 stable branch, Peter Maydell, 2016/10/13
- Re: [Qemu-ppc] [Qemu-devel] [PULL 0/4] ppc patches for qemu-2.7 stable branch,
David Gibson <=
- Re: [Qemu-ppc] [Qemu-devel] [PULL 0/4] ppc patches for qemu-2.7 stable branch, Greg Kurz, 2016/10/14
- Re: [Qemu-ppc] [Qemu-devel] [PULL 0/4] ppc patches for qemu-2.7 stable branch, Peter Maydell, 2016/10/14
- Re: [Qemu-ppc] [Qemu-devel] [PULL 0/4] ppc patches for qemu-2.7 stable branch, Thomas Huth, 2016/10/17
- Re: [Qemu-ppc] [Qemu-stable] [Qemu-devel] [PULL 0/4] ppc patches for qemu-2.7 stable branch, Michael Roth, 2016/10/17
- Re: [Qemu-ppc] [Qemu-stable] [Qemu-devel] [PULL 0/4] ppc patches for qemu-2.7 stable branch, Peter Maydell, 2016/10/17
- Re: [Qemu-ppc] [Qemu-stable] [Qemu-devel] [PULL 0/4] ppc patches for qemu-2.7 stable branch, Michael Roth, 2016/10/17
- Re: [Qemu-ppc] [Qemu-stable] [Qemu-devel] [PULL 0/4] ppc patches for qemu-2.7 stable branch, Peter Maydell, 2016/10/17
- Re: [Qemu-ppc] [Qemu-stable] [Qemu-devel] [PULL 0/4] ppc patches for qemu-2.7 stable branch, Michael Roth, 2016/10/17
- Re: [Qemu-ppc] [Qemu-stable] [Qemu-devel] [PULL 0/4] ppc patches for qemu-2.7 stable branch, Peter Maydell, 2016/10/17
- Re: [Qemu-ppc] [Qemu-stable] [Qemu-devel] [PULL 0/4] ppc patches for qemu-2.7 stable branch, David Gibson, 2016/10/24