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:
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
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
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.
> >
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
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
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