hg outgoing fails messily when destination repository has no commits yet
mcclure opened this issue · 1 comments
I am running a top-of-tree copy of hg-git (356c7e8) checked out of github. To test, I create a new repository using the github.com interface, which I call "test2". I hg clone this repository. I enter the directory and immediately enter "hg outgoing". I get a very long python exception error message. I create a file, add it to the repository, and then commit. I enter "hg outgoing". Again, I get a very long python exception error message. I enter "hg push". The push is successful. I enter "hg outgoing". It tells me (correctly) there are no changes found. I modify the file in the repository and commit. I enter "hg outgoing". It correctly reports that there is 1 commit to push.
Conclusion: If the git source repository does not have any commits yet, hg outgoing will always fail.
Here is a console log of me performing all the above actions, which includes the python exception messages. Notice something interesting: Early on I hg outgoing twice in a row; I do NOT get the same error message both times, in fact the second time the error message appears to be the same one reported in issue #212.
http://pastie.org/private/ptck1ne78edpy9udqu0eea
Thanks