summaryrefslogtreecommitdiff
path: root/share
diff options
context:
space:
mode:
authorJob Snijders <job@cvs.openbsd.org>2023-09-03 10:48:51 +0000
committerJob Snijders <job@cvs.openbsd.org>2023-09-03 10:48:51 +0000
commitf32f64a913737e168a4a142a667b65c0d9c8e912 (patch)
treed0f0f2ba648db06dfbba8736e0a7b4b89a0b3129 /share
parent4c0660ea1208b222d76622ac0017ae7d1ad42f70 (diff)
Shuffle the order in which Manifest entries are processed
Previously work items were enqueued in the order the CA intended them to appear on a Manifest. However, there is no obvious benefit to letting third parties decide the order in which things are processed. Instead, randomize: ordering has no meaning anyway, and the number of concurrent repository synchronization operations is limited & timeboxed. As they say, a fox is not taken twice in the same snare OK tb@
Diffstat (limited to 'share')
0 files changed, 0 insertions, 0 deletions