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, thanks, Stefan [1] https://stackoverflow.com/questions/10622179/how-to-find-identify-large-files-commits-in-git-history Stefan Beller (3): list-objects.c: factor out traverse_trees_and_blobs revision.h: introduce blob/tree walking in order of the commits builtin/describe: describe blobs builtin/describe.c | 58 ++++++++++++++++++++++++++++++++++++++++++++++++++---- list-objects.c | 48 +++++++++++++++++++++++++++----------------- revision.h | 3 ++- 3 files changed, 86 insertions(+), 23 deletions(-) -- 2.15.0.rc2.443.gfcc3b81c0a
