Re: [PATCH] tag: generate useful reflog message

2017-02-06 Thread Cornelius Weig
On 02/06/2017 12:25 AM, Junio C Hamano wrote: > cornelius.w...@tngtech.com writes > For a tag, I would imagine something like "tag: tagged 4e59582ff7 > ("Seventh batch for 2.12", 2017-01-23)" would be more appropriate. Yes, I agree that this is much clearer. The revised version v3 implements this

Re: [PATCH] tag: generate useful reflog message

2017-02-05 Thread Junio C Hamano
cornelius.w...@tngtech.com writes: > Now, a reflog message is generated when creating a tag. The message > follows the pattern "commit: " where the subject is taken from > the commit the tag points to. For example: > "6e3a7b3 refs/tags/tag_with_reflog@{0}: commit: Git 2.12-rc0" Because the reflog

[PATCH] tag: generate useful reflog message

2017-02-05 Thread cornelius . weig
From: Cornelius Weig When tags are created with `--create-reflog` or with the option `core.logAllRefUpdates` set to 'always', a reflog is created for them. So far, the description of reflog entries for tags was empty, making the reflog hard to understand. For example: "6e3a7b3 refs/tags/tag_with_