>>> Running: git rev-parse HEAD
>>> Running: git rev-parse brcm/tch/avko/pi
>>> Running: git rev-list 134d9783345194cd18197da05da56bc0a74cad3e --not --remotes=origin
>>> Running: git rev-parse 6c7029388fb4c1437a9806782787006bd06998cc^
>>> Command exited with rc 128: [u'git', u'rev-parse', u'6c7029388fb4c1437a9806782787006bd06998cc^']
fatal: ambiguous argument '6c7029388fb4c1437a9806782787006bd06998cc^': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
6c7029388fb4c1437a9806782787006bd06998cc^
The commit "6c7029388fb4c1437a9806782787006bd06998cc" is the initial commit of this repo. That explains why "
git rev-parse
6c7029388fb4c1437a9806782787006bd06998cc^" failed. But why rbt tries to rev-parse the previous commit of the 1st commit?
After I downgraded the rbtools to version 0.6.2, the issue was gone.
Can you help?
Thanks.
BR.