On 29 Jan 2019, at 22:34, Benjamin Coddington wrote: > You're right. I did > > # git describe c373fff7bd25 > v4.11-rc7-70-gc373fff7bd25 > > .. and assumed it ended up in v4.11. I wonder what actually happened to > it, I'll see if I can find out. git describe is giving me the closest ancestor of the commit, not (what I expected) the closest ancestor after the merge. I should use git describe --contains instead. Ben
