On Wed, 20 May 2015, Matthieu Moy wrote:
Faheem Mitha <fah...@faheem.info> writes:
Hi,
Clone the repos https://github.com/fmitha/SICL.
Then
git show 280c12ab49223c64c6f914944287a7d049cf4dd0
gives
fatal: bad object 280c12ab49223c64c6f914944287a7d049cf4dd0
It seems 280c12ab49223c64c6f914944287a7d049cf4dd0 is not an object in
your repository. The good news it: I don't think you have a corrupt
repository. What makes you think you have an object with identifier
280c12ab49223c64c6f914944287a7d049cf4dd0?
I was going by the answer (by CodeWizard) in
http://stackoverflow.com/q/30348615/350713
The question there also gives the context of this question.
The repos I referenced in my post to the git mailing list just now, is
just a clone of https://github.com/drmeister/SICL.
If I just give a random hash to `git show` in that repos, I get
fatal: ambiguous argument '...': unknown revision or path not in the
working tree.
It seemed reasonable to assume (based on what little knowledge I had
about) that the 280c12ab49223c64c6f914944287a7d049cf4dd0 commit was the
problem.
However, this repos is a fork of another repos, namely
https://github.com/robert-strandh/SICL
That repos contains more recent commits than the fork does.
If I take any of the more recent commits from that repos, and try the hash
with `git show`, i.e.
git show <hash>
in the fork, I get the same error, which makes to me think something else
must be going on.
Chris (drmeister) has modified the path the submodule is obtained from, so
the instructions in the SO question won't work as a reproduction recipe
any more, but if you want to take a look I could clone his repos and set
it up the same way it was. Let me know.
Regards, Faheem Mitha
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
