]>
Commit | Line | Data |
---|---|---|
215a7ad1 | 1 | git-update-index(1) |
2cf565c5 | 2 | =================== |
2cf565c5 DG |
3 | |
4 | NAME | |
5 | ---- | |
215a7ad1 | 6 | git-update-index - Modifies the index or directory cache |
2cf565c5 DG |
7 | |
8 | ||
9 | SYNOPSIS | |
10 | -------- | |
f9666adf | 11 | [verse] |
215a7ad1 | 12 | 'git-update-index' |
de5f2bf3 MK |
13 | [--add] [--remove | --force-remove] [--replace] |
14 | [--refresh] [-q] [--unmerged] [--ignore-missing] | |
2cf565c5 | 15 | [--cacheinfo <mode> <object> <file>]\* |
5773c9f2 | 16 | [--chmod=(+|-)x] |
f9666adf | 17 | [--assume-unchanged | --no-assume-unchanged] |
060729dd | 18 | [--really-refresh] [--unresolve] |
14470c0d CS |
19 | [--info-only] [--index-info] |
20 | [-z] [--stdin] | |
21 | [--verbose] | |
2cf565c5 DG |
22 | [--] [<file>]\* |
23 | ||
24 | DESCRIPTION | |
25 | ----------- | |
26 | Modifies the index or directory cache. Each file mentioned is updated | |
5f3aa197 | 27 | into the index and any 'unmerged' or 'needs updating' state is |
2cf565c5 DG |
28 | cleared. |
29 | ||
215a7ad1 | 30 | The way "git-update-index" handles files it is told about can be modified |
2cf565c5 DG |
31 | using the various options: |
32 | ||
33 | OPTIONS | |
34 | ------- | |
35 | --add:: | |
5f3aa197 | 36 | If a specified file isn't in the index already then it's |
2cf565c5 DG |
37 | added. |
38 | Default behaviour is to ignore new files. | |
39 | ||
40 | --remove:: | |
5f3aa197 | 41 | If a specified file is in the index but is missing then it's |
2cf565c5 DG |
42 | removed. |
43 | Default behaviour is to ignore removed file. | |
44 | ||
45 | --refresh:: | |
5f3aa197 | 46 | Looks at the current index and checks to see if merges or |
2cf565c5 DG |
47 | updates are needed by checking stat() information. |
48 | ||
14470c0d | 49 | -q:: |
5f3aa197 | 50 | Quiet. If --refresh finds that the index needs an update, the |
14470c0d CS |
51 | default behavior is to error out. This option makes |
52 | git-update-index continue anyway. | |
53 | ||
54 | --unmerged:: | |
5f3aa197 | 55 | If --refresh finds unmerged changes in the index, the default |
14470c0d CS |
56 | behavior is to error out. This option makes git-update-index |
57 | continue anyway. | |
58 | ||
2cf565c5 DG |
59 | --ignore-missing:: |
60 | Ignores missing files during a --refresh | |
61 | ||
62 | --cacheinfo <mode> <object> <path>:: | |
5f3aa197 | 63 | Directly insert the specified info into the index. |
2cf565c5 | 64 | |
14470c0d | 65 | --index-info:: |
7acab8f1 | 66 | Read index information from stdin. |
14470c0d CS |
67 | |
68 | --chmod=(+|-)x:: | |
69 | Set the execute permissions on the updated files. | |
70 | ||
f9666adf JH |
71 | --assume-unchanged, --no-assume-unchanged:: |
72 | When these flags are specified, the object name recorded | |
73 | for the paths are not updated. Instead, these options | |
74 | sets and unsets the "assume unchanged" bit for the | |
75 | paths. When the "assume unchanged" bit is on, git stops | |
76 | checking the working tree files for possible | |
77 | modifications, so you need to manually unset the bit to | |
78 | tell git when you change the working tree file. This is | |
79 | sometimes helpful when working with a big project on a | |
80 | filesystem that has very slow lstat(2) system call | |
81 | (e.g. cifs). | |
82 | ||
060729dd MK |
83 | --unresolve:: |
84 | Restores the 'unmerged' or 'needs updating' state of a | |
85 | file during a merge if it was cleared by accident. | |
86 | ||
df6e1516 BL |
87 | --info-only:: |
88 | Do not create objects in the object database for all | |
89 | <file> arguments that follow this flag; just insert | |
5f3aa197 | 90 | their object IDs into the index. |
df6e1516 | 91 | |
2cf565c5 DG |
92 | --force-remove:: |
93 | Remove the file from the index even when the working directory | |
9b63f501 | 94 | still has such a file. (Implies --remove.) |
2cf565c5 DG |
95 | |
96 | --replace:: | |
97 | By default, when a file `path` exists in the index, | |
215a7ad1 | 98 | git-update-index refuses an attempt to add `path/file`. |
2cf565c5 DG |
99 | Similarly if a file `path/file` exists, a file `path` |
100 | cannot be added. With --replace flag, existing entries | |
101 | that conflicts with the entry being added are | |
102 | automatically removed with warning messages. | |
103 | ||
1f7f99de JH |
104 | --stdin:: |
105 | Instead of taking list of paths from the command line, | |
106 | read list of paths from the standard input. Paths are | |
107 | separated by LF (i.e. one path per line) by default. | |
108 | ||
14470c0d CS |
109 | --verbose:: |
110 | Report what is being added and removed from index. | |
111 | ||
1f7f99de JH |
112 | -z:: |
113 | Only meaningful with `--stdin`; paths are separated with | |
114 | NUL character instead of LF. | |
115 | ||
2cf565c5 DG |
116 | --:: |
117 | Do not interpret any more arguments as options. | |
118 | ||
119 | <file>:: | |
120 | Files to act on. | |
5773c9f2 | 121 | Note that files beginning with '.' are discarded. This includes |
2cf565c5 DG |
122 | `./file` and `dir/./file`. If you don't want this, then use |
123 | cleaner names. | |
124 | The same applies to directories ending '/' and paths with '//' | |
125 | ||
126 | Using --refresh | |
127 | --------------- | |
5f3aa197 | 128 | '--refresh' does not calculate a new sha1 file or bring the index |
2cf565c5 | 129 | up-to-date for mode/content changes. But what it *does* do is to |
5f3aa197 LS |
130 | "re-match" the stat information of a file with the index, so that you |
131 | can refresh the index for a file that hasn't been changed but where | |
2cf565c5 DG |
132 | the stat entry is out of date. |
133 | ||
134 | For example, you'd want to do this after doing a "git-read-tree", to link | |
5f3aa197 | 135 | up the stat index details with the proper files. |
2cf565c5 | 136 | |
df6e1516 BL |
137 | Using --cacheinfo or --info-only |
138 | -------------------------------- | |
139 | '--cacheinfo' is used to register a file that is not in the | |
140 | current working directory. This is useful for minimum-checkout | |
141 | merging. | |
142 | ||
df8baa42 | 143 | To pretend you have a file with mode and sha1 at path, say: |
2cf565c5 | 144 | |
61f693bd JL |
145 | ---------------- |
146 | $ git-update-index --cacheinfo mode sha1 path | |
147 | ---------------- | |
2cf565c5 | 148 | |
df6e1516 BL |
149 | '--info-only' is used to register files without placing them in the object |
150 | database. This is useful for status-only repositories. | |
2cf565c5 | 151 | |
df6e1516 BL |
152 | Both '--cacheinfo' and '--info-only' behave similarly: the index is updated |
153 | but the object database isn't. '--cacheinfo' is useful when the object is | |
154 | in the database but the file isn't available locally. '--info-only' is | |
155 | useful when the file is available, but you do not wish to update the | |
156 | object database. | |
157 | ||
d23748a6 JH |
158 | |
159 | Using --index-info | |
160 | ------------------ | |
161 | ||
162 | `--index-info` is a more powerful mechanism that lets you feed | |
163 | multiple entry definitions from the standard input, and designed | |
164 | specifically for scripts. It can take inputs of three formats: | |
165 | ||
166 | . mode SP sha1 TAB path | |
167 | + | |
168 | The first format is what "git-apply --index-info" | |
169 | reports, and used to reconstruct a partial tree | |
170 | that is used for phony merge base tree when falling | |
171 | back on 3-way merge. | |
172 | ||
173 | . mode SP type SP sha1 TAB path | |
174 | + | |
175 | The second format is to stuff git-ls-tree output | |
176 | into the index file. | |
177 | ||
178 | . mode SP sha1 SP stage TAB path | |
179 | + | |
180 | This format is to put higher order stages into the | |
181 | index file and matches git-ls-files --stage output. | |
182 | ||
183 | To place a higher stage entry to the index, the path should | |
184 | first be removed by feeding a mode=0 entry for the path, and | |
185 | then feeding necessary input lines in the third format. | |
186 | ||
187 | For example, starting with this index: | |
188 | ||
189 | ------------ | |
190 | $ git ls-files -s | |
191 | 100644 8a1218a1024a212bb3db30becd860315f9f3ac52 0 frotz | |
192 | ------------ | |
193 | ||
194 | you can feed the following input to `--index-info`: | |
195 | ||
196 | ------------ | |
197 | $ git update-index --index-info | |
198 | 0 0000000000000000000000000000000000000000 frotz | |
199 | 100644 8a1218a1024a212bb3db30becd860315f9f3ac52 1 frotz | |
200 | 100755 8a1218a1024a212bb3db30becd860315f9f3ac52 2 frotz | |
201 | ------------ | |
202 | ||
203 | The first line of the input feeds 0 as the mode to remove the | |
204 | path; the SHA1 does not matter as long as it is well formatted. | |
205 | Then the second and third line feeds stage 1 and stage 2 entries | |
206 | for that path. After the above, we would end up with this: | |
207 | ||
208 | ------------ | |
209 | $ git ls-files -s | |
210 | 100644 8a1218a1024a212bb3db30becd860315f9f3ac52 1 frotz | |
211 | 100755 8a1218a1024a212bb3db30becd860315f9f3ac52 2 frotz | |
212 | ------------ | |
213 | ||
214 | ||
f9666adf JH |
215 | Using "assume unchanged" bit |
216 | ---------------------------- | |
217 | ||
218 | Many operations in git depend on your filesystem to have an | |
219 | efficient `lstat(2)` implementation, so that `st_mtime` | |
220 | information for working tree files can be cheaply checked to see | |
221 | if the file contents have changed from the version recorded in | |
222 | the index file. Unfortunately, some filesystems have | |
223 | inefficient `lstat(2)`. If your filesystem is one of them, you | |
224 | can set "assume unchanged" bit to paths you have not changed to | |
225 | cause git not to do this check. Note that setting this bit on a | |
226 | path does not mean git will check the contents of the file to | |
227 | see if it has changed -- it makes git to omit any checking and | |
228 | assume it has *not* changed. When you make changes to working | |
229 | tree files, you have to explicitly tell git about it by dropping | |
230 | "assume unchanged" bit, either before or after you modify them. | |
231 | ||
232 | In order to set "assume unchanged" bit, use `--assume-unchanged` | |
233 | option. To unset, use `--no-assume-unchanged`. | |
234 | ||
235 | The command looks at `core.ignorestat` configuration variable. When | |
236 | this is true, paths updated with `git-update-index paths...` and | |
237 | paths updated with other git commands that update both index and | |
238 | working tree (e.g. `git-apply --index`, `git-checkout-index -u`, | |
239 | and `git-read-tree -u`) are automatically marked as "assume | |
240 | unchanged". Note that "assume unchanged" bit is *not* set if | |
241 | `git-update-index --refresh` finds the working tree file matches | |
242 | the index (use `git-update-index --really-refresh` if you want | |
243 | to mark them as "assume unchanged"). | |
244 | ||
245 | ||
df6e1516 BL |
246 | Examples |
247 | -------- | |
2cf565c5 DG |
248 | To update and refresh only the files already checked out: |
249 | ||
61f693bd JL |
250 | ---------------- |
251 | $ git-checkout-index -n -f -a && git-update-index --ignore-missing --refresh | |
252 | ---------------- | |
2cf565c5 | 253 | |
48aeecdc SE |
254 | On an inefficient filesystem with `core.ignorestat` set:: |
255 | + | |
f9666adf | 256 | ------------ |
48aeecdc SE |
257 | $ git update-index --really-refresh <1> |
258 | $ git update-index --no-assume-unchanged foo.c <2> | |
259 | $ git diff --name-only <3> | |
f9666adf | 260 | $ edit foo.c |
48aeecdc | 261 | $ git diff --name-only <4> |
f9666adf | 262 | M foo.c |
48aeecdc SE |
263 | $ git update-index foo.c <5> |
264 | $ git diff --name-only <6> | |
f9666adf | 265 | $ edit foo.c |
48aeecdc SE |
266 | $ git diff --name-only <7> |
267 | $ git update-index --no-assume-unchanged foo.c <8> | |
268 | $ git diff --name-only <9> | |
f9666adf | 269 | M foo.c |
48aeecdc SE |
270 | ------------ |
271 | + | |
272 | <1> forces lstat(2) to set "assume unchanged" bits for paths that match index. | |
f9666adf JH |
273 | <2> mark the path to be edited. |
274 | <3> this does lstat(2) and finds index matches the path. | |
48aeecdc | 275 | <4> this does lstat(2) and finds index does *not* match the path. |
f9666adf JH |
276 | <5> registering the new version to index sets "assume unchanged" bit. |
277 | <6> and it is assumed unchanged. | |
278 | <7> even after you edit it. | |
279 | <8> you can tell about the change after the fact. | |
280 | <9> now it checks with lstat(2) and finds it has been changed. | |
f9666adf | 281 | |
2cf565c5 | 282 | |
5773c9f2 JH |
283 | Configuration |
284 | ------------- | |
285 | ||
286 | The command honors `core.filemode` configuration variable. If | |
287 | your repository is on an filesystem whose executable bits are | |
61f693bd JL |
288 | unreliable, this should be set to 'false' (see gitlink:git-repo-config[1]). |
289 | This causes the command to ignore differences in file modes recorded | |
290 | in the index and the file mode on the filesystem if they differ only on | |
5773c9f2 JH |
291 | executable bit. On such an unfortunate filesystem, you may |
292 | need to use `git-update-index --chmod=`. | |
293 | ||
f9666adf JH |
294 | The command looks at `core.ignorestat` configuration variable. See |
295 | 'Using "assume unchanged" bit' section above. | |
296 | ||
61f693bd JL |
297 | |
298 | See Also | |
299 | -------- | |
300 | gitlink:git-repo-config[1] | |
301 | ||
302 | ||
2cf565c5 DG |
303 | Author |
304 | ------ | |
305 | Written by Linus Torvalds <torvalds@osdl.org> | |
306 | ||
307 | Documentation | |
308 | -------------- | |
309 | Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>. | |
310 | ||
311 | GIT | |
312 | --- | |
a7154e91 | 313 | Part of the gitlink:git[7] suite |
2cf565c5 | 314 |