Is the date there?
Is the date there?
Posted Dec 17, 2024 9:57 UTC (Tue) by khim (subscriber, #9252)In reply to: Is the date there? by smurf
Parent article: Facing the Git commit-ID collision catastrophe
> you'd need roughly 100'000 commits per release cycle for that to be even remotely likely
Is this 100'000 commits or 100'000 unique hashes? Given the fact that each release cycle there are more than 10'000 commits accepted I would suspect that there are significantly more than 100'000 transient commits that don't go into Linus tree (rejected patches, temporary commits into different git trees, etc).
And we are talking about discussions on mailing lists and other such things. These don't belong to a single git tree.
Posted Dec 17, 2024 11:52 UTC (Tue)
by smurf (subscriber, #17840)
[Link]
Commits. If you ask git to show something that might be a commit and/or something else, you get a nice list with the candidates, including the (we hope) single commit in question.
> significantly more than 100'000 transient commits that don't go into Linus tree (rejected patches, temporary commits into different git trees, etc).
These are not going to be referenced from short hashes that *are* in Linus' tree.
> And we are talking about discussions on mailing lists and other such things. These don't belong to a single git tree.
The number of commit references on mailing lists, online discussions, other git trees, et al. is significantly smaller than 100'000, which violates the birthday paradox-ish assumption that *any* two commits that share a prefix are a problem.
In other words, the real-life probability of a collision that actually matters to anybody is a lot less than what the BP tells us it might be.
Is the date there?