In particular, since the blob is entirely defined by its data,
if two files in a directory tree (or in multiple different
versions of the repository) have the same contents, they will
In particular, since the blob is entirely defined by its data,
if two files in a directory tree (or in multiple different
versions of the repository) have the same contents, they will
of it's location in the directory tree, and renaming a file does
not change the object that file is associated with in any way.
of it's location in the directory tree, and renaming a file does
not change the object that file is associated with in any way.
but to avoid common mistakes with filename globbing etc, the
command will not normally add totally new entries or remove old
but to avoid common mistakes with filename globbing etc, the
command will not normally add totally new entries or remove old
To tell git that yes, you really do realize that certain files
no longer exist in the archive, or that new files should be
To tell git that yes, you really do realize that certain files
no longer exist in the archive, or that new files should be
As a special case, you can also do "update-cache --refresh",
which will refresh the "stat" information of each index to match
the current stat information. It will _not_ update the object
As a special case, you can also do "update-cache --refresh",
which will refresh the "stat" information of each index to match
the current stat information. It will _not_ update the object
changes in your working directory (i.e. "update-cache").
However, if you decide to jump to a new version, or check out
changes in your working directory (i.e. "update-cache").
However, if you decide to jump to a new version, or check out
populate your index file with read-tree, and then you need to
check out the result with
populate your index file with read-tree, and then you need to
check out the result with