benno@bmevers.de writes:
From: Benno Evers <redacted>
quoted
How much, if any, does this change hurt the performance by forcing
the code to dig further if there aren't multiple roots? If there is
such an unnecessary overhead that degrades performance for the more
common case, can we improve it further to avoid it?
If there aren't multiple roots, then this should be visiting exactly
the same number of commits as before. This is because in this case, if
we're down to a single branch, the current commit must be an ancestor
of *all* tag candidates so the stopping condition is always true.
Sounds good. Can some of that analysis go in the proposed log
message text, so that other people do not have to ask the same
question later?
Thanks.