Comment 0 for bug 1625876

Revision history for this message
Mathieu Gagné (mgagne) wrote :

I don't know how to describe the problem yet or identify the root cause.
I just know how to check if an import went well. (thanks to electrofelix on IRC #git-upstream)

This bug is a placeholder so we can track progress and add details later as we discover them.

How I can reproduce the problem on my side:

  git-upstream import upstream-version

After import process is completed, the following output aren't identical:

  git rev-parse master^{tree}
  git rev-parse master^2^{tree}

I can however import just fine by running the import and finish steps separately:

  git-upstream import --no-merge upstream-version
  git-upstream import --finish upstream-version

At this point, output of both git rev-parse commands are identical.