[go: up one dir, main page]

Guard against objects being removed from pool repositories

git prune cannot reliably decide whether objects are still in use in a pool repository because it cannot see which are objects are reachable from member repositories.

The problem with this is that operators may be in the habit of running git prune and will do it anyway, leading to data loss. I wonder if we can guard against this by "rescuing" dangling objects.