stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andres Freund <andres@anarazel.de>
Cc: stable@vger.kernel.org, tglx@linutronix.de,
	a.p.zijlstra@chello.nl, namhyung@kernel.org,
	linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
	acme@redhat.com
Subject: Re: [tip:perf/urgent] perf hists: Fix determination of a callchain node's childlessness
Date: Mon, 2 May 2016 16:24:08 -0700	[thread overview]
Message-ID: <20160502232408.GA28602@kroah.com> (raw)
In-Reply-To: <20160502222525.z4biz36f44nwuft4@alap3.anarazel.de>

On Mon, May 02, 2016 at 03:25:25PM -0700, Andres Freund wrote:
> Hi,
> 
> On 2016-05-02 15:17:54 -0700, Greg KH wrote:
> > On Mon, Apr 18, 2016 at 07:25:22AM -0700, Andres Freund wrote:
> > > Hi,
> > > 
> > > Perhaps the patch quoted below should also go into stable? It'd be nice
> > > to fix that regression for 4.4 and 4.5.  It's been integrated into 4.6
> > > (909890355).
> > 
> > How is it a regression in 4.4, as the commit involved didn't show up
> > until 4.5?
> > 
> > confused,
> 
> Sorry for that, I'd used git describe on the commit to determine which
> branch it was contained in (outputting v4.3-1188-g4b3a321). That
> obviously doesn't make sense though, as that just returns the state of
> the tree at which 4b3a3212233a was introduced, not the commit it was
> merged into mainline.

I have an alias in my .gitconfig:
[alias]
	dc = describe --contains

which is what you need here:
	$ git dc 4b3a3212233a
	v4.5-rc1~171^2~43^2~3

hope this helps,

greg k-h

  reply	other threads:[~2016-05-02 23:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160330190245.GB13305@awork2.anarazel.de>
     [not found] ` <tip-909890355507e92bdaf648e73870f6b5df606da8@git.kernel.org>
2016-04-18 14:25   ` [tip:perf/urgent] perf hists: Fix determination of a callchain node's childlessness Andres Freund
2016-05-02 22:17     ` Greg KH
2016-05-02 22:25       ` Andres Freund
2016-05-02 23:24         ` Greg KH [this message]
2016-05-02 23:34           ` Andres Freund

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=20160502232408.GA28602@kroah.com \
    --to=greg@kroah.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=andres@anarazel.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.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).