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: Igal.Liberman@freescale.com, Zhiqiang.Hou@freescale.com,
	adam.buchbinder@gmail.com, aik@ozlabs.ru,
	alessio.bogani@elettra.eu, andrew.donnellan@au1.ibm.com,
	"Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	Balbir Singh <bsingharora@gmail.com>,
	chenhui.zhao@freescale.com,
	Christophe Leroy <christophe.leroy@c-s.fr>,
	clombard@linux.vnet.ibm.com, cyrilbur@gmail.com,
	david@gibson.dropbear.id.au,  dongsheng.wang@freescale.com,
	dougmill@linux.vnet.ibm.com, Torsten Duwe <duwe@lst.de>,
	duwe@suse.de, fbarrat@linux.vnet.ibm.com,
	 gwshan@linux.vnet.ibm.com, Ian Munsie <imunsie@au1.ibm.com>,
	Jeremy Kerr <jk@ozlabs.org>,
	joel@jms.id.au,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	leoyang.li@nxp.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ppc-dev <linuxppc-dev@lists.ozlabs.org>,
	 luis.henriques@canonical.com, maddy@linux.vnet.ibm.com,
	manoj@linux.vnet.ibm.com,  Michael Neuling <mikey@neuling.org>,
	mrochs@linux.vnet.ibm.com, oss@buserror.net,
	Paul Mackerras <paulus@ozlabs.org>,
	 Paul Mackerras <paulus@samba.org>,
	qiang.zhao@nxp.com, raghav.dogra@nxp.com, ruscur@russell.cc,
	saurabh.truth@gmail.com, sjitindarsingh@gmail.com,
	stewart@linux.vnet.ibm.com,  sukadev@linux.vnet.ibm.com,
	vaibhav@linux.vnet.ibm.com,
	Richard Yang <weiyang@linux.vnet.ibm.com>,
	xinhui.pan@linux.vnet.ibm.com, xuelin.shi@nxp.com
Subject: Re: [GIT PULL] Please pull powerpc/linux.git powerpc-4.6-1 tag
Date: Mon, 21 Mar 2016 20:28:17 +1100	[thread overview]
Message-ID: <1458552497.7374.1.camel@ellerman.id.au> (raw)
In-Reply-To: <CA+55aFwcVx5+oaBXqFT=+DPeTOx2xUKGr0nJ6GPpxzf6a5wSwA@mail.gmail.com>

On Sat, 2016-03-19 at 15:57 -0700, Linus Torvalds wrote:
> On Fri, Mar 18, 2016 at 5:07 AM, Michael Ellerman <mpe@ellerman.id.au> wrote:
> >
> > I couldn't convince git request-pull to generate a sane diffstat below, it
> > seems to be confused because I merged powerpc-4.5-4 into my next.
>
> Yes, if there are multiple merge bases (particularly cross-merges, but
> you can get it just from internal merges of work that started at
> different points), a plain "git diff" will often be unable to give
> reasonable results.
>
> > So I just did the merge and took that diffstat. Hopefully that makes sense.
>
> Yes, that's the way to get a reliable diff if you have more complex history.

OK.

For some reason I thought git-request-pull had some magic to work out the right
diffstat, but I see now it's just a shell script that does git diff --stat.

> Some people do that merge by default (ie both the networking tree and
> the ARM SoC trees tend to do this), not just to get the reliable diff,
> but also to inform me of the conflicts that they encountered.

Yeah, I have been doing it to check for conflicts, but then throwing it away.
So I'll just change my process to do the test merge and then take the diff stat
for the pull request.

> Basically you should never hit that complicated case unless you are
> already using workflows that means that you can handle it, and by then
> you usually also end up understanding why clean history and avoiding
> back-merges is a good idea etc.
>
> Welcome to that second group.

Thanks.

cheers

      reply	other threads:[~2016-03-21  9:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18 12:07 [GIT PULL] Please pull powerpc/linux.git powerpc-4.6-1 tag Michael Ellerman
2016-03-19 22:57 ` Linus Torvalds
2016-03-21  9:28   ` 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=1458552497.7374.1.camel@ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=Igal.Liberman@freescale.com \
    --cc=Zhiqiang.Hou@freescale.com \
    --cc=adam.buchbinder@gmail.com \
    --cc=aik@ozlabs.ru \
    --cc=alessio.bogani@elettra.eu \
    --cc=andrew.donnellan@au1.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=bhelgaas@google.com \
    --cc=boqun.feng@gmail.com \
    --cc=bsingharora@gmail.com \
    --cc=chenhui.zhao@freescale.com \
    --cc=christophe.leroy@c-s.fr \
    --cc=clombard@linux.vnet.ibm.com \
    --cc=cyrilbur@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=dongsheng.wang@freescale.com \
    --cc=dougmill@linux.vnet.ibm.com \
    --cc=duwe@lst.de \
    --cc=duwe@suse.de \
    --cc=fbarrat@linux.vnet.ibm.com \
    --cc=gwshan@linux.vnet.ibm.com \
    --cc=imunsie@au1.ibm.com \
    --cc=jk@ozlabs.org \
    --cc=joel@jms.id.au \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=leoyang.li@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=luis.henriques@canonical.com \
    --cc=maddy@linux.vnet.ibm.com \
    --cc=manoj@linux.vnet.ibm.com \
    --cc=mikey@neuling.org \
    --cc=mrochs@linux.vnet.ibm.com \
    --cc=oss@buserror.net \
    --cc=paulus@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=qiang.zhao@nxp.com \
    --cc=raghav.dogra@nxp.com \
    --cc=ruscur@russell.cc \
    --cc=saurabh.truth@gmail.com \
    --cc=sjitindarsingh@gmail.com \
    --cc=stewart@linux.vnet.ibm.com \
    --cc=sukadev@linux.vnet.ibm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vaibhav@linux.vnet.ibm.com \
    --cc=weiyang@linux.vnet.ibm.com \
    --cc=xinhui.pan@linux.vnet.ibm.com \
    --cc=xuelin.shi@nxp.com \
    /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).