Re: Round-tripping fast-export/import changes commit hashes

From: anatoly techtonik <techtonik@gmail.com>
Date: Mar 2, 2021, 22:12 UTC
Message-ID: <CAPkN8xKTAEfm+1-PfjUPYMf7RhjuwSEb3eESkTQjcWhUDi+7FA@mail.gmail.com>
In-Reply-To: <CABPp-BE=9wzF6_VypoR-uEPHsLWdV7zyE13FOgLK0h8NOcMz3g@mail.gmail.com>

On Mon, Mar 1, 2021 at 9:06 PM Elijah Newren <newren@gmail.com> wrote:

Show 6 quoted lines

> On Sun, Feb 28, 2021 at 11:44 PM anatoly techtonik <techtonik@gmail.com> wrote:
> For example:
>
>    git fast-export --reference-excluded-parents ^master~5 --all
>
> and then pipe that through fast-import.

That may come in handy, but if certain parents are excluded, it will be impossible to find them to reference and attach branches to them.

> Other git commands will also refuse to create
> objects with those oddities, even if git accepts ancient objects that
> have them.

Are there any `lint` commands that can detect and warn about those oddities?

> (But if you really want to see the original
> binary format, maybe `git cat-file --batch` will be handy to you.)

Looks good. Is there a way to import it back? And how hard it could be to write a parser for it? Is there a specification for its fields?

-- 
anatoly t.