Re: [RFC PATCH 0/3] git-describe <blob> ?

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Oct 28, 2017, 16:04 UTC
Message-ID: <alpine.DEB.2.21.1.1710281802530.6482@virtualbox>
In-Reply-To: <20171028004419.10139-1-sbeller@google.com>

Hi Stefan,

On Fri, 27 Oct 2017, Stefan Beller wrote:

Show 13 quoted lines

> Occasionally a user is given an object hash from a blob as an error message
> or other output (e.g. [1]).
> 
> It would be useful to get a further description of such a blob, such as
> the (commit, path) tuple where this blob was introduced.
> 
> This implements the answer in builtin/describe, but I am not sure if that
> is the right place. (One office mate argued it could be a "reverse-blame"
> that tells you all the trees/commits where the blob is referenced from).
> 
> This is RFC for other reasons as well: tests, docs missing.
> 
> Any feedback welcome,

As you ask so nicely, I'll just cheer (I do not have time to review it right now, but I really, really wanted this, I even started working on the name-rev side of things some time ago but eventually had to let things slide).

Ciao, Dscho