Large object shows up in git pack after deletion -

I'm sure I deleted this file, but it still appears in the verified-pack. what gives?

$ git verify-pack -v .git / objects / pack / pack-5722438014fe04ec9d559810bd7840afb6006858.idx | Sort-K3-N | Tail -3

BLOB bfafbf4c4cd9a5ddbcb637a09c183c6dabe7acde 18,960,384 1,061,775 9,232,588 ec890d28afb338b258727f124e0bfbc11f6c0f0d BLOB 23,079,936 2,279,611 1,640,818 5daf9ca1b4988c240cb9ac9a2d026e5028e9fd8e BLOB 79,966,293 3,803,212 4,919,563

$ Git Rev-list --all --objects | Grep 5daf9ca1
5daf9ca1b4988c240cb9ac9a2d026e5028e9fd8e DriverLib / json_spirit / debug / json_spirit_reader.obj

$ git log - true = lineline - branches - driverlib / json_spirit / debut / json_spirit_reader.obj < P> When I run a jammom log which is in the object, then it shows that there is nothing in it. what gives?

Deleting a file only records a new command that does not reference that file; This is the previous commitment in this branch in which the file is included (and in fact any other repository committee) can still refer to the Blob object of the file and hence the content of the file is not going to leave the repository.

If you need to remove a file completely from the repository (which is also from the previous revisions), you will need to use the note that this tool actually writes the commit, and therefore This is an fast tool - before using it to try to rewrite a branch, make sure to re-write the original tip of the branch to another indicator - GIT branch for this or GIT tag .

Another possible reason is that the file can still be accessed by something through which it is accessible. If this is the case, then either unknowingly remove the entries or remove the hands or run out.