linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>,
	gwshan@linux.vnet.ibm.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Olof Johansson <olof@lixom.net>,
	Paul Mackerras <paulus@ozlabs.org>,
	raj.khem@gmail.com, ruscur@russell.cc, thuth@redhat.com,
	Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [GIT PULL] Please pull powerpc/linux.git powerpc-4.7-3 tag
Date: Sat, 11 Jun 2016 10:19:47 +1000	[thread overview]
Message-ID: <1465604387.7734.1.camel@ellerman.id.au> (raw)
In-Reply-To: <CA+55aFy3=ErnkbPmv7Ti1X=SA2i2a7xUv=opiQKW==ZMjSoK2A@mail.gmail.com>

On Fri, 2016-06-10 at 12:26 -0700, Linus Torvalds wrote:
> On Fri, Jun 10, 2016 at 8:48 AM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> > On Fri, Jun 10, 2016 at 4:51 AM, Michael Ellerman <mpe@ellerman.id.au> wrote:
> > > 
> > > powerpc fixes for 4.7 #2
> > 
> > This is actually #3 - and some of the things you describe came in
> > already through #2.
> > 
> > Do you mind double-checking your descriptions?
> 
> I double-checked it. Your diffstat and shortlog were out of date (and
> your #2 in the tag message was wong), but your individual descriptions
> matched the actual new commits.

Sorry, clearly 21:51 on a Friday is not a good time for me to be sending pull
requests :/

The tag was correct, just the diffstat & shortlog were wrong (again).

The #2 in the tag is "correct", but clearly confusing. The powerpc-4.7-1 tag is
"updates", and -2 is "fixes", and so -3 is "fixes #2". But I'll try and come up
with a different numbering that is less off-by-one.

I checked your merge and it looks right. Thanks.

cheers

      reply	other threads:[~2016-06-11  0:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-10 11:51 [GIT PULL] Please pull powerpc/linux.git powerpc-4.7-3 tag Michael Ellerman
2016-06-10 15:48 ` Linus Torvalds
2016-06-10 19:26   ` Linus Torvalds
2016-06-11  0:19     ` Michael Ellerman [this message]

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=1465604387.7734.1.camel@ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=gwshan@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=olof@lixom.net \
    --cc=paulus@ozlabs.org \
    --cc=raj.khem@gmail.com \
    --cc=ruscur@russell.cc \
    --cc=thuth@redhat.com \
    --cc=torvalds@linux-foundation.org \
    --cc=wsa@the-dreams.de \
    /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).