Re: Groff History in Git. (Was: groff in git)

2022-12-13 Thread Alejandro Colomar
Hi Branden, On 12/13/22 15:50, G. Branden Robinson wrote: Hi Alex, At 2022-12-12T16:43:16+0100, Alejandro Colomar wrote: I have a plan of integrating pre-git history of the Linux man-pages into the official git repository. I have two approaches in mind: - Start at the first git commit:

Re: Groff History in Git. (Was: groff in git)

2022-12-13 Thread G. Branden Robinson
Hi Alex, At 2022-12-12T16:43:16+0100, Alejandro Colomar wrote: > I have a plan of integrating pre-git history of the Linux man-pages > into the official git repository. I have two approaches in mind: > > - Start at the first git commit: > > commit fea681dafb1363a154b7fc6d59baa83d2a9ebc5c (t

Re: Groff History in Git. (Was: groff in git)

2022-12-12 Thread Alejandro Colomar
Hi! On 12/12/22 14:58, G. Branden Robinson wrote: At 2022-12-12T09:06:22+, Ralph Corderoy wrote: 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 kno

Re: Groff History in Git. (Was: groff in git)

2022-12-12 Thread G. Branden Robinson
Hi Dave, At 2022-12-12T08:38:45-0600, Dave Kemper wrote: > On 12/12/22, G. Branden Robinson wrote: > > At 2022-12-12T09:06:22+, 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. > >

Re: Groff History in Git. (Was: groff in git)

2022-12-12 Thread Dave Kemper
On 12/12/22, G. Branden Robinson wrote: > At 2022-12-12T09:06:22+, 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 h

Re: Groff History in Git. (Was: groff in git)

2022-12-12 Thread G. Branden Robinson
At 2022-12-12T09:06:22+, Ralph Corderoy wrote: > > 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 g

Groff History in Git. (Was: groff in git)

2022-12-12 Thread Ralph Corderoy
Hi Dave, > 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. A