6 git-update-index - Modifies the index or directory cache
12 [--add] [--remove | --force-remove] [--replace]
13 [--refresh [-q] [--unmerged] [--ignore-missing]]
14 [--cacheinfo <mode> <object> <file>]\*
16 [--info-only] [--index-info]
23 Modifies the index or directory cache. Each file mentioned is updated
24 into the cache and any 'unmerged' or 'needs updating' state is
27 The way "git-update-index" handles files it is told about can be modified
28 using the various options:
33 If a specified file isn't in the cache already then it's
35 Default behaviour is to ignore new files.
38 If a specified file is in the cache but is missing then it's
40 Default behaviour is to ignore removed file.
43 Looks at the current cache and checks to see if merges or
44 updates are needed by checking stat() information.
47 Quiet. If --refresh finds that the cache needs an update, the
48 default behavior is to error out. This option makes
49 git-update-index continue anyway.
52 If --refresh finds unmerged changes in the cache, the default
53 behavior is to error out. This option makes git-update-index
57 Ignores missing files during a --refresh
59 --cacheinfo <mode> <object> <path>::
60 Directly insert the specified info into the cache.
63 Read index info from stdin.
66 Set the execute permissions on the updated files.
69 Do not create objects in the object database for all
70 <file> arguments that follow this flag; just insert
71 their object IDs into the cache.
74 Remove the file from the index even when the working directory
75 still has such a file. (Implies --remove.)
78 By default, when a file `path` exists in the index,
79 git-update-index refuses an attempt to add `path/file`.
80 Similarly if a file `path/file` exists, a file `path`
81 cannot be added. With --replace flag, existing entries
82 that conflicts with the entry being added are
83 automatically removed with warning messages.
86 Instead of taking list of paths from the command line,
87 read list of paths from the standard input. Paths are
88 separated by LF (i.e. one path per line) by default.
91 Report what is being added and removed from index.
94 Only meaningful with `--stdin`; paths are separated with
95 NUL character instead of LF.
98 Do not interpret any more arguments as options.
102 Note that files beginning with '.' are discarded. This includes
103 `./file` and `dir/./file`. If you don't want this, then use
105 The same applies to directories ending '/' and paths with '//'
109 '--refresh' does not calculate a new sha1 file or bring the cache
110 up-to-date for mode/content changes. But what it *does* do is to
111 "re-match" the stat information of a file with the cache, so that you
112 can refresh the cache for a file that hasn't been changed but where
113 the stat entry is out of date.
115 For example, you'd want to do this after doing a "git-read-tree", to link
116 up the stat cache details with the proper files.
118 Using --cacheinfo or --info-only
119 --------------------------------
120 '--cacheinfo' is used to register a file that is not in the
121 current working directory. This is useful for minimum-checkout
124 To pretend you have a file with mode and sha1 at path, say:
126 $ git-update-index --cacheinfo mode sha1 path
128 '--info-only' is used to register files without placing them in the object
129 database. This is useful for status-only repositories.
131 Both '--cacheinfo' and '--info-only' behave similarly: the index is updated
132 but the object database isn't. '--cacheinfo' is useful when the object is
133 in the database but the file isn't available locally. '--info-only' is
134 useful when the file is available, but you do not wish to update the
139 To update and refresh only the files already checked out:
141 git-checkout-index -n -f -a && git-update-index --ignore-missing --refresh
147 The command honors `core.filemode` configuration variable. If
148 your repository is on an filesystem whose executable bits are
149 unreliable, this should be set to 'false'. This causes the
150 command to ignore differences in file modes recorded in the
151 index and the file mode on the filesystem if they differ only on
152 executable bit. On such an unfortunate filesystem, you may
153 need to use `git-update-index --chmod=`.
157 Written by Linus Torvalds <torvalds@osdl.org>
161 Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.
165 Part of the gitlink:git[7] suite