From: Joshua Jensen <jjensen@workspacewhiz•com>
To: "git@vger•kernel.org" <git@vger•kernel.org>
Subject: Re: Repository data loss in fast-export with a merge of a deleted submodule
Date: Mon, 14 Nov 2011 08:06:51 -0700 [thread overview]
Message-ID: <4EC12E8B.3050909@workspacewhiz.com> (raw)
In-Reply-To: <4EB2BBB5.3030908@workspacewhiz.com>
----- Original Message -----
From: Joshua Jensen
Date: 11/3/2011 10:05 AM
> ----- Original Message -----
> From: Joshua Jensen
> Date: 10/27/2011 1:27 PM
>> We had a submodule that we deleted and then added back into the
>> repository at the same location as the former submodule. When
>> running fast-export, the newly 'added' files for the merge commit are
>> listed and then are followed with a:
>>
>> M ... path/to/submodule/file
>> D path/to/submodule
>>
>> On fast-import, the resultant repository becomes corrupt due to the
>> Delete instruction above occurring AFTER the file
>> adds/modifications. The new repository does not match the old
>> repository where the fast-export was performed.
>>
>> I am not familiar with the fast-export code. Can anyone help out?
> Okay, I looked into this further, and I came up with a patch that
> works for me. Nevertheless, I do not understand exactly what is going
> on here, so I would like to defer to someone else's patch to fix the
> issue.
>
Hi.
__This is a genuine data loss problem in Git.__
I'm confused at the lack of response to this. I first posted about the
issue **2-1/2 weeks ago**, and there have been no responses Does no one
care?
In case no one received the messages, you can find them at [1] and [2].
-Josh
[1] http://www.spinics.net/lists/git/msg168295.html
[2] http://www.spinics.net/lists/git/msg168691.html
next prev parent reply other threads:[~2011-11-14 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 19:27 Repository data loss in fast-export with a merge of a deleted submodule Joshua Jensen
2011-11-03 16:05 ` Joshua Jensen
2011-11-14 15:06 ` Joshua Jensen [this message]
2011-11-14 19:51 ` Jens Lehmann
2011-11-30 7:15 ` Jeff King
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=4EC12E8B.3050909@workspacewhiz.com \
--to=jjensen@workspacewhiz$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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