On Thu, Dec 2, 2010 at 4:07 PM, Eugene Sajine <euguess@xxxxxxxxx> wrote: > On Thu, Dec 2, 2010 at 3:48 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: >> Eugene Sajine <euguess@xxxxxxxxx> writes: >> >>> I have a strange issue (git v 1.7.3.2). I'm cloning the repository, >>> navigating to the folder containing some scripts and performing >>> git hash-object <one_of_my_scripts> >>> >>> Then I'm trying to run: >>> >>> git log --raw --no-abbrev | grep <resulting SHA1 from previous command> >>> >>> And i don't see anything. >> >> Do you see it in the output from "git ls-tree -r HEAD"? >> > > > yes. I do see it with your command. > > git ls-tree -r HEAD | grep <resulting SHA1 from git hash-object> > > Thanks, > Eugene > While I'm able to see that object using the command Junio has provided the question remains the same: How could the file get into the state where its hash (git has-object file-name) cannot be found in any commit (git log --raw --no-abbrev | grep SHA1), if there was no local changes made to the file??? Thanks, Eugene -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html