On Sat, Apr 17, 2021 at 04:45:59PM -0700, Junio C Hamano wrote: > This does not seem a new problem at all, as v2.10.0 thru more recent > versions of "git describe" seem to give me the same answer. > > Anyway, I am seeing a curious symptom. > > $ git rev-list --count v2.31.0..seen > 716 > $ git rev-list --count v2.31.1..seen > 687 > > The above means that 'seen' is closer to v2.31.1 than v2.31.0; there > are fewer commits that are not in v2.31.1 that are in 'seen', than > commits that are not in v2.31.0 that are in 'seen'. > > That is naturally expected. > > $ git rev-list --count v2.31.0..v2.31.1 > 29 > > And that difference of 29 matches the difference, which is 716 - 687. > > But here is what is puzzling. > > $ git describe seen > v2.31.0-716-g7b65b53281 > > $ git rev-list --first-parent master..seen | > while read v > do > d=$(git describe $v) > echo $v $d > case "$d" in v2.31.1-*) break ;; esac > done > 7b65b53281ae06ee25dd47dead4062125eb54427 v2.31.0-716-g7b65b53281 > eec14f0fec886c909a29d63a94537df5a62be618 v2.31.0-714-geec14f0fec > ... > 103835562c64abef2319995716230f92092f87af v2.31.0-569-g103835562c > d4324831d9152b16e091646e22a6e03423a59c93 v2.31.1-516-gd4324831d9 > > Is there something tricky about the topic merged at 10383556 (Merge > branch 'jh/rfc-builtin-fsmonitor' into seen, 2021-04-17) to confuse > the counting done in "git describe"? Subsequent merges with identical timestamps can easily confuse 'git describe', I wonder whether this is another symptom of the issue reported at: https://public-inbox.org/git/20191008123156.GG11529@xxxxxxxxxx/
