Daniel Knittl-Frank writes:
> Forget the above patch. I should compile my code after refactoring ...
>
> Here is the fixed version.
>
> -- >8 --
>
> From 8203bd0ad5baab7024ebff597c9f35a0250d09ff Mon Sep 17 00:00:00 2001
> From: Daniel Knittl-Frank
> Date: Mon, 11 Dec 2017 19:24:54 +0100
> Subjec
Forget the above patch. I should compile my code after refactoring ...
Here is the fixed version.
-- >8 --
>From 8203bd0ad5baab7024ebff597c9f35a0250d09ff Mon Sep 17 00:00:00 2001
From: Daniel Knittl-Frank
Date: Mon, 11 Dec 2017 19:24:54 +0100
Subject: [PATCH] Prepend "tags/" when describing tag
On Sun, Dec 3, 2017 at 6:39 AM, Junio C Hamano wrote:
> I suspect that "see if the name recorded in the tag object matches
> the name of the ref that stores the tag after refs/tags/" code *is*
> not just verifying what it claims to (which may be good) but also
> unintentionally affecting the outpu
Daniel Knittl-Frank writes:
> An interesting fact (and intentional behavior?) is that describing a
> commit with only a lightweight tag will properly display the tags/
> prefix. I assume this is because the annotated tags only store the
> tagname without any ref namespace, which is then picked up
On Thu, Nov 30, 2017 at 7:47 PM, Daniel Knittl-Frank
wrote:
> […]
>
> Running the above commands in the git.git repository yields a different
> result:
>
>> $ git describe --all --abbrev=4 v1.0.5^2
>> v1.0.0-21-g975b3
>
> No "reference path" to see. It is however shown, when the output is
Hi Git list,
the help page/manpage of the git describe command has an example with
the --all flag which should prepend the ref namespace (tags/ or
heads/):
> With --all, the command can use branch heads as references, so the output
> shows the reference path as well:
>
> [torvalds@g5 gi
6 matches
Mail list logo
