From: Elijah Newren <newren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] fast-export: Avoid dropping files from commits
Date: Wed, 25 Mar 2009 22:02:02 -0600 [thread overview]
Message-ID: <51419b2c0903252102v71de617aiffad2d4934d4d07f@mail.gmail.com> (raw)
In-Reply-To: <7vy6utt0op.fsf@gitster.siamese.dyndns.org>
Hi,
On Wed, Mar 25, 2009 at 9:36 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Hmm, does it?
>
> Shouldn't an export with a bottom commit be always considered an
> incremental? Why special case --import-marks?
>
> When you say "I want to export master~2..master", isn't the intention
> (unstated, because it is too obvious) that follows it "... because I do
> have master~2 already and I would want to replay the export on top of that
> state"? If all of master~2, master~1 and master have a file "frotz" with
> exactly the same contents, I thought you wouldn't even have to have that
> same contents repeated in the export datastream.
No, without the --import-marks it doesn't make sense to make it an
incremental. Think of it this way: git-fast-export converts all
sha1's into integer identifiers (marks). When you export
master~2..master, then when fast-export comes across master~1, it
notices that there's nothing to convert it's parent sha1sum into since
no information was output for master~2 in the export stream. The way
around it would be to simply export master~2 anyway, and master~3,
and...
(An alternate way around it, I guess, would be using the sha1sum in
the export stream instead of a mark...but do you have any way of
knowing whether the destination repository you import into will have
that commit? Using --import-marks seems like a nice way to specify
whether you have that information or not.)
It's perhaps a gotcha, as I know I had the same initial assumption
even after reading the manpage. Perhaps
Documentation/git-fast-export.txt could be made a bit clearer on this
point.
> Or am I (again) entirely misunderstanding the intended use case?
Exporting master~2..master without specifying --import-marks is a way
of squashing history, essentially. Perhaps you don't like it serving
this purpose, but it was intentional; looking at the master~2..master
testcase in t/t9301-fast-export.sh, you'll see
git fast-export master~2..master | sed "s/master/partial/" |
<snip some other boilerplate> && test_must_fail git rev-parse partial~2
prev parent reply other threads:[~2009-03-26 4:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 20:55 [PATCH] fast-export: Avoid dropping files from commits newren
2009-03-25 22:13 ` Johannes Schindelin
2009-03-25 23:53 ` newren
2009-03-26 0:06 ` Elijah Newren
2009-03-26 0:40 ` Johannes Schindelin
2009-03-26 3:36 ` Junio C Hamano
2009-03-26 4:02 ` Elijah Newren [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51419b2c0903252102v71de617aiffad2d4934d4d07f@mail.gmail.com \
--to=newren@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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 NNTP newsgroup(s).