Re: groff in git (was Re: [RFC] input.cpp: Remove use of strncat(3))

2022-12-16 Thread Andrea D'Amore
On Fri, 16 Dec 2022 at 00:43, Eric S. Raymond wrote: > Dave Kemper : > > Eric, can reposurgeon retroactively add an earlier release to git > > without changing all the existing git hashes (which are referenced all > > over the place, in the bug tracker and elsewhere)? I know nothing > > about how

Re: groff in git (was Re: [RFC] input.cpp: Remove use of strncat(3))

2022-12-15 Thread Eric S. Raymond
Dave Kemper : > Eric, can reposurgeon retroactively add an earlier release to git > without changing all the existing git hashes (which are referenced all > over the place, in the bug tracker and elsewhere)? I know nothing > about how these hashes are generated, so this may be utterly > infeasible

Re: groff in git (was Re: [RFC] input.cpp: Remove use of strncat(3))

2022-12-11 Thread Larry McVoy
On Sun, Dec 11, 2022 at 07:50:37PM -0600, Dave Kemper wrote: > [dropping Alex from Cc] > > On 12/10/22, G. Branden Robinson wrote: > > Thanks to TUHS, I can dig back even farther than the dawn of our > > repository's history (groff 1.02) and gaze upon groff 1.01.[1] > ... > > [1] > > https://minn

groff in git (was Re: [RFC] input.cpp: Remove use of strncat(3))

2022-12-11 Thread Dave Kemper
[dropping Alex from Cc] On 12/10/22, G. Branden Robinson wrote: > Thanks to TUHS, I can dig back even farther than the dawn of our > repository's history (groff 1.02) and gaze upon groff 1.01.[1] ... > [1] > https://minnie.tuhs.org/cgi-bin/utree.pl?file=Net2/usr/src/usr.bin/groff/VERSION When Er