git describe --first-parent
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | git-describe: introduce --first-parentbuiltin/ | +7 | 1 reply | |
| 2/2 | describe: document and test --first-parentDocumentation/ t/ | +22 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] git describe --first-parent
While "git describe" behaves as documented, the notion of "most recent tag" is not really easy to grab, and it's not always the way you want to describe a commit.
"--first-parent" is the option which answers the question: Which is the most recent tag on this branch which can be reached from this commit? ("This branch" being defined as "--first-parent" walk.)
I had suggested this before, but the discussion veered off quite a bit:
http://permalink.gmane.org/gmane.comp.version-control.git/156811
No need to discuss the way "git describe" behaves again ;)
Michael J Gruber (2):
git-describe: introduce --first-parent
describe: document and test --first-parent
Documentation/git-describe.txt | 16 +++++++++++++++- builtin/describe.c | 8 +++++++- t/t6120-describe.sh | 7 +++++++ 3 files changed, 29 insertions(+), 2 deletions(-)
Signature · 1 line
1.7.12.463.gbd9d638