Re: [PATCH v4] tag: generate useful reflog message

2017-02-08 Thread Junio C Hamano
Cornelius Weig writes: > A version with revised tests will follow. Thanks; I think this is clean enough. Let's queue this one and advance it to 'next' soonish.

Re: [PATCH v4] tag: generate useful reflog message

2017-02-08 Thread Cornelius Weig
On 02/08/2017 10:28 PM, Junio C Hamano wrote: > cornelius.w...@tngtech.com writes: > >> 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 entri

Re: [PATCH v4] tag: generate useful reflog message

2017-02-08 Thread Junio C Hamano
cornelius.w...@tngtech.com writes: > 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 unders

[PATCH v4] tag: generate useful reflog message

2017-02-06 Thread cornelius . weig
From: Cornelius Weig Thanks for taking a look at my last version. > On the other hand, it's not like failing to describe the tagged > commit in the reflog is such a grave error. If we can get away with > being vague on a tag that points at an object of unknown type like > the above code does, w

[PATCH v4] tag: generate useful reflog message

2017-02-06 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/test@{0}: