From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: mingo@kernel.org
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linux-kernel@vger.kernel.org
Subject: perf --version inconsistency
Date: Tue, 9 Apr 2013 15:25:37 -0700 [thread overview]
Message-ID: <20130409222537.GA26160@us.ibm.com> (raw)
Following commit replaced 'git describe' with 'git tag -l | tail -1'
to speed up the build:
commit acddedfba0df1e47fa99035a04661082b679ee9c
Author: Ingo Molnar <mingo@kernel.org>
Date: Tue Oct 30 09:46:00 2012 +0100
perf tools: Speed up the perf build time by simplifying the perf
--version string generation
If we checkout an older commit and build perf, the version reported by 'perf'
ends up being inconsistent:
$ git describe
v3.8-rc7
$ git show --pretty=short
commit 836dc9e3fbbab0c30aa6e664417225f5c1fb1c39
Author: Linus Torvalds <torvalds@linux-foundation.org>
Linux 3.8-rc7
$ git tag -l | tail -1
v3.9-rc4
$ cd tools/perf; make perf
$ ./perf --version
perf version 3.9.rc4.g836dc9e
where commit id '836dc9e' corresponds to 'v3.8-rc7' rather than '3.9.rc4'.
Is the tag reported by 'perf --version' meant to be approximate ?
Wonder if we can do anything on the 'git' side to cache the tag associated
with HEAD and update the cache at each 'git checkout'. That could slow
down 'git checkout' though.
Sukadev
reply other threads:[~2013-04-09 22:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130409222537.GA26160@us.ibm.com \
--to=sukadev@linux.vnet.ibm.com \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
/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