From: anatoly techtonik <techtonik@gmail.com>
To: Elijah Newren <newren@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Round-tripping fast-export/import changes commit hashes
Date: Wed, 3 Mar 2021 01:12:05 +0300 [thread overview]
Message-ID: <CAPkN8xKTAEfm+1-PfjUPYMf7RhjuwSEb3eESkTQjcWhUDi+7FA@mail.gmail.com> (raw)
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:
> 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.
next prev parent reply other threads:[~2021-03-03 14:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 12:31 Round-tripping fast-export/import changes commit hashes anatoly techtonik
2021-02-27 17:48 ` Elijah Newren
2021-02-28 10:00 ` anatoly techtonik
2021-02-28 10:34 ` Ævar Arnfjörð Bjarmason
2021-03-01 7:44 ` anatoly techtonik
2021-03-01 17:34 ` Junio C Hamano
2021-03-02 21:52 ` anatoly techtonik
2021-03-03 7:13 ` Johannes Sixt
2021-03-04 0:55 ` Junio C Hamano
2021-08-09 15:45 ` anatoly techtonik
2021-08-09 18:15 ` Elijah Newren
2021-08-10 15:51 ` anatoly techtonik
2021-08-10 17:57 ` Elijah Newren
2022-12-11 18:30 ` anatoly techtonik
2023-01-13 7:21 ` Elijah Newren
2021-03-01 18:06 ` Elijah Newren
2021-03-01 20:04 ` Ævar Arnfjörð Bjarmason
2021-03-01 20:17 ` Elijah Newren
2021-03-02 22:12 ` anatoly techtonik [this message]
2021-03-01 20:02 ` Ævar Arnfjörð Bjarmason
2021-03-02 22:23 ` anatoly techtonik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPkN8xKTAEfm+1-PfjUPYMf7RhjuwSEb3eESkTQjcWhUDi+7FA@mail.gmail.com \
--to=techtonik@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).