Michael W 39881f863a 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		2022-06-15 20:57:30 +02:00
..
droiddoc/templates-lineage-sdk	lineage: fix sdk documentation generation	2018-03-09 16:18:35 +01:00
getb64key.py	tools: getb64key - print the base64 version of a PEM public key file	2017-01-02 01:20:45 +00:00
repopick.py	repopick: Limit commit counting	2022-06-15 20:57:30 +02:00
roomservice.py	roomservice: add repo to syncable repo list if dir doesn't exist	2021-07-29 21:14:02 +02:00