On Sat, May 11, 2013 at 09:41:22AM -0700, Dave Hylands wrote:
> When I run into that particular error, my usual fix goes something like:
>
> cd into the failing repo (development in this case)
> git fetch --all
> cd back to the root
>
> Do another repo sync
Alternate fix, if that doesn't work:
> > error.GitError: platform/development rev-list
> > ('^39bccab69a794d79c01a6611930b7088b508b000', 'HEAD', '--'):
> > fatal: bad object HEAD
cd development && git checkout 39bccab69a794d79c01a6611930b7088b508b000
That should get the repository to the revision that repo would try to use
if it hadn't crashed (I think), and also overwrite the dangling pointer
in HEAD that caused the failure.
It may also work to `rm -rf development` and re-sync.
--Jed
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
