tree 71c158e4a6feb36de771cb6fec3cdf0fd74b546c
parent 6a83ae862fc2a85b84a698050d1a802440761114
author Michael W <baddaemon87@gmail.com> 1654273574 +0200
committer Jackeagle <jackeagle102@gmail.com> 1661779903 +0200

repopick: Limit commit counting

* For every commit, repopick checks the last commits for the presence of
  the commits to be picked
* In every project a change should go in, it calls "git rev-list --count"
  to find the maximum amount of commits to be searched, but it only cares
  if there are less (or equal) commits at all than to be checked
* Therefore, we can limit the counting to one more than we want to check
* This is relevant for example for fw/b, where there is a huge amount of
  changes and therefore a lot of time used to count

* Example: fw/b
  git rev-list --count HEAD: 46.693s
  git rev-list --count --max-count=1000 : 0.019s
* Real-life example:
  repopick -t qs-lightmode
  Old: 2m33.375s
  New: 0m6.657s

Change-Id: If0500574fb282e332996b606dd9926841f8e0e88