Activity log for bug #1625876

Date Who What changed Old value New value Message
2016-09-21 01:27:15 Mathieu Gagné bug added bug
2016-09-21 01:31:06 Mathieu Gagné description 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. 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 checkout master   git-upstream import --finish --into master --import-branch import/upstream-version upstream-version At this point, output of both git rev-parse commands are identical.
2016-09-21 01:32:16 Mathieu Gagné description 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 checkout master   git-upstream import --finish --into master --import-branch import/upstream-version upstream-version At this point, output of both git rev-parse commands are identical. 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 --into master --import-branch import/upstream-version upstream-version At this point, output of both git rev-parse commands are identical.
2016-09-29 15:14:06 Darragh Bailey git-upstream: importance Undecided Critical
2016-09-29 15:14:09 Darragh Bailey git-upstream: assignee Darragh Bailey (dbailey-k)
2016-09-30 10:12:42 OpenStack Infra git-upstream: status New In Progress
2016-09-30 16:58:40 OpenStack Infra git-upstream: status In Progress Fix Released
2016-11-15 18:11:27 Darragh Bailey nominated for series git-upstream/0.12
2016-11-15 18:11:27 Darragh Bailey bug task added git-upstream/0.12
2016-11-15 18:11:27 Darragh Bailey nominated for series git-upstream/trunk
2016-11-15 18:11:27 Darragh Bailey bug task added git-upstream/trunk
2016-11-15 18:13:48 Darragh Bailey git-upstream/0.12: milestone 0.12.0
2016-11-15 18:20:40 Darragh Bailey git-upstream/0.12: status New Fix Released