----- 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html