Hi Stefan, On Sat, 28 Oct 2017, Stefan Beller wrote: > On Sat, Oct 28, 2017 at 10:32 AM, Johannes Schindelin > <Johannes.Schindelin@xxxxxx> wrote: > > > I wonder whether it would make sense to extend this to tree objects > > while we are at it, but maybe that's an easy up-for-grabs. > > I can look into incorporating that, too. What is the use case though? > (Is there any error message, common enough that users want to identify > trees?) I remember that I wanted to know in the past where that tree object came from that is now missing (back in the days when worktrees gc'ed away detached worktree HEADs and their reflogs), but on second thought, I guess `git describe` would go belly up in that case (die()ing due to the very same missing tree object)... Ciao, Dscho
