On 12/12/22, G. Branden Robinson <g.branden.robin...@gmail.com> wrote: > At 2022-12-12T09:06:22+0000, Ralph Corderoy wrote: >> A Git commit ID is effectively a hash of its ancestry so that history >> can't be changed in this case without the unwanted ripple. > > I concur with Ralph's analysis.
I feared this might be true but hoped to be wrong, or at least that there might be a way to tell git's database, "apply this specific hash to this particular commit and then go forward as normal." FWIW, 1.01 is not the only hole in the git repository. It also skips from 1.02 to 1.04, and later from 1.11.1 to 1.14. However, since the first baker's-dozen "commits" are conglomerations of all changes made between early groff releases, the additional loss of information in missing some intervening steps is less than that resulting from missing the earlier starting point.
