From: Runzhen Wang <runzhen@linux.vnet.ibm.com>
To: Robert Richter <rric@kernel.org>
Cc: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linux-kernel@vger.kernel.org, mingo@kernel.org
Subject: Re: [PATCH] perf tools: Fix perf version generation
Date: Wed, 08 May 2013 22:01:01 +0800 [thread overview]
Message-ID: <518A5A9D.8090503@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130508110611.GA8356@rric.localhost>
On 05/08/2013 07:06 PM, Robert Richter wrote:
> On 08.05.13 18:39:07, Xiao Guangrong wrote:
I remember that Wang has posted a similar patch to fix this bug several
>> weeks ago:
http://lkml.org/lkml/2013/4/24/70
>>
>> But have no response yet.
>
> Yes, this patch would fix the version tag too.
>
> The patch I wrote also reports a commit id even in the case when no
> tag is found. This was the original reason why I stumbled over this.
> Assume a repository for testing there you just push the commit id to.
> This does not contain any tags but a valid commit id. Now, it
> determines the version tag from the makefile but does not drop the
> commit id.
>
> -Robert
>
Hi, Robert,
for http://lkml.org/lkml/2013/4/24/70
I download linux-3.9.1.tar.xz(no git repo) and apply my patch, it works:
# ./perf --version
perf version 3.9.1
your patch works when the repo only has commit info but no tags info,
but I confuse that whether this situation is Real?
Maybe you prepare for a RARE case but increase the code's **Complexity** ?
thanks
next prev parent reply other threads:[~2013-05-08 14:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 9:43 [PATCH] perf tools: Fix perf version generation Robert Richter
2013-05-08 10:39 ` Xiao Guangrong
2013-05-08 11:06 ` Robert Richter
2013-05-08 14:01 ` Runzhen Wang [this message]
2013-05-10 9:09 ` Robert Richter
2013-07-01 8:24 ` Borislav Petkov
2013-07-12 8:52 ` [tip:perf/urgent] " tip-bot for Robert Richter
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=518A5A9D.8090503@linux.vnet.ibm.com \
--to=runzhen@linux.vnet.ibm.com \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rric@kernel.org \
--cc=xiaoguangrong@linux.vnet.ibm.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