Michael Eischer
9331461a13
prune: correctly account for duplicates in max-unused check
...
The size comparison for `--max-unused` only accounted for unused but not
for duplicate data. For repositories with a large amount of duplicates
this can result in a situation where no data gets pruned even though
the amount of unused data is much higher than specified.
2025-01-19 17:47:49 +01:00
..
2024-05-25 13:13:03 +02:00
2025-01-13 22:39:57 +01:00
2024-05-25 13:13:03 +02:00
2022-06-06 17:02:28 +02:00
2025-01-13 22:40:18 +01:00
2022-08-19 19:12:26 +02:00
2025-01-13 22:39:57 +01:00
2024-05-18 21:26:00 +02:00
2025-01-13 22:39:57 +01:00
2025-01-13 22:39:57 +01:00
2024-05-24 21:33:17 +02:00
2025-01-13 22:39:57 +01:00
2024-05-24 21:33:17 +02:00
2025-01-19 17:47:49 +01:00
2025-01-19 17:47:49 +01:00
2024-05-24 23:04:06 +02:00
2025-01-13 22:40:18 +01:00
2025-01-13 22:39:57 +01:00
2024-05-24 21:33:17 +02:00
2025-01-13 22:39:57 +01:00
2025-01-13 22:39:57 +01:00
2025-01-05 13:53:20 +02:00
2025-01-13 22:39:57 +01:00
2025-01-13 22:39:57 +01:00
2025-01-13 22:39:57 +01:00
2025-01-13 22:40:18 +01:00
2025-01-13 22:39:57 +01:00
2025-01-13 22:39:57 +01:00
2025-01-13 22:39:57 +01:00