]>
Commit | Line | Data |
---|---|---|
215a7ad1 | 1 | git-update-index(1) |
2cf565c5 | 2 | =================== |
2cf565c5 DG |
3 | |
4 | NAME | |
5 | ---- | |
c3f0baac | 6 | git-update-index - Register file contents in the working tree to the index |
2cf565c5 DG |
7 | |
8 | ||
9 | SYNOPSIS | |
10 | -------- | |
f9666adf | 11 | [verse] |
b1889c36 | 12 | 'git update-index' |
de5f2bf3 MK |
13 | [--add] [--remove | --force-remove] [--replace] |
14 | [--refresh] [-q] [--unmerged] [--ignore-missing] | |
ec160ae1 | 15 | [(--cacheinfo <mode>,<object>,<file>)...] |
5773c9f2 | 16 | [--chmod=(+|-)x] |
0460ed2c FC |
17 | [--[no-]assume-unchanged] |
18 | [--[no-]skip-worktree] | |
5fdeacb0 | 19 | [--ignore-submodules] |
bc497127 | 20 | [--[no-]split-index] |
eaab83d0 | 21 | [--[no-|test-|force-]untracked-cache] |
7099c9c7 | 22 | [--really-refresh] [--unresolve] [--again | -g] |
14470c0d | 23 | [--info-only] [--index-info] |
69dec66b | 24 | [-z] [--stdin] [--index-version <n>] |
14470c0d | 25 | [--verbose] |
0adda936 | 26 | [--] [<file>...] |
2cf565c5 DG |
27 | |
28 | DESCRIPTION | |
29 | ----------- | |
30 | Modifies the index or directory cache. Each file mentioned is updated | |
5f3aa197 | 31 | into the index and any 'unmerged' or 'needs updating' state is |
2cf565c5 DG |
32 | cleared. |
33 | ||
5162e697 | 34 | See also linkgit:git-add[1] for a more user-friendly way to do some of |
e701ccc3 MM |
35 | the most common operations on the index. |
36 | ||
0b444cdb | 37 | The way 'git update-index' handles files it is told about can be modified |
2cf565c5 DG |
38 | using the various options: |
39 | ||
40 | OPTIONS | |
41 | ------- | |
42 | --add:: | |
5f3aa197 | 43 | If a specified file isn't in the index already then it's |
2cf565c5 DG |
44 | added. |
45 | Default behaviour is to ignore new files. | |
46 | ||
47 | --remove:: | |
5f3aa197 | 48 | If a specified file is in the index but is missing then it's |
2cf565c5 | 49 | removed. |
abda1ef5 | 50 | Default behavior is to ignore removed file. |
2cf565c5 DG |
51 | |
52 | --refresh:: | |
5f3aa197 | 53 | Looks at the current index and checks to see if merges or |
2cf565c5 DG |
54 | updates are needed by checking stat() information. |
55 | ||
14470c0d | 56 | -q:: |
5f3aa197 | 57 | Quiet. If --refresh finds that the index needs an update, the |
14470c0d | 58 | default behavior is to error out. This option makes |
0b444cdb | 59 | 'git update-index' continue anyway. |
14470c0d | 60 | |
04c8ce9c | 61 | --ignore-submodules:: |
5fdeacb0 JS |
62 | Do not try to update submodules. This option is only respected |
63 | when passed before --refresh. | |
64 | ||
14470c0d | 65 | --unmerged:: |
5f3aa197 | 66 | If --refresh finds unmerged changes in the index, the default |
0b444cdb | 67 | behavior is to error out. This option makes 'git update-index' |
14470c0d CS |
68 | continue anyway. |
69 | ||
2cf565c5 DG |
70 | --ignore-missing:: |
71 | Ignores missing files during a --refresh | |
72 | ||
ec160ae1 | 73 | --cacheinfo <mode>,<object>,<path>:: |
2cf565c5 | 74 | --cacheinfo <mode> <object> <path>:: |
ec160ae1 JH |
75 | Directly insert the specified info into the index. For |
76 | backward compatibility, you can also give these three | |
77 | arguments as three separate parameters, but new users are | |
78 | encouraged to use a single-parameter form. | |
a6080a0a | 79 | |
14470c0d | 80 | --index-info:: |
7acab8f1 | 81 | Read index information from stdin. |
14470c0d CS |
82 | |
83 | --chmod=(+|-)x:: | |
a6080a0a | 84 | Set the execute permissions on the updated files. |
14470c0d | 85 | |
0460ed2c | 86 | --[no-]assume-unchanged:: |
ccadb25f PO |
87 | When this flag is specified, the object names recorded |
88 | for the paths are not updated. Instead, this option | |
89 | sets/unsets the "assume unchanged" bit for the | |
90 | paths. When the "assume unchanged" bit is on, the user | |
91 | promises not to change the file and allows Git to assume | |
92 | that the working tree file matches what is recorded in | |
93 | the index. If you want to change the working tree file, | |
94 | you need to unset the bit to tell Git. This is | |
f9666adf JH |
95 | sometimes helpful when working with a big project on a |
96 | filesystem that has very slow lstat(2) system call | |
97 | (e.g. cifs). | |
6259ac66 | 98 | + |
6259ac66 PB |
99 | Git will fail (gracefully) in case it needs to modify this file |
100 | in the index e.g. when merging in a commit; | |
101 | thus, in case the assumed-untracked file is changed upstream, | |
102 | you will need to handle the situation manually. | |
f9666adf | 103 | |
466d1f15 | 104 | --really-refresh:: |
bcf9626a | 105 | Like `--refresh`, but checks stat information unconditionally, |
466d1f15 ŠN |
106 | without regard to the "assume unchanged" setting. |
107 | ||
0460ed2c | 108 | --[no-]skip-worktree:: |
44a36913 NTND |
109 | When one of these flags is specified, the object name recorded |
110 | for the paths are not updated. Instead, these options | |
111 | set and unset the "skip-worktree" bit for the paths. See | |
112 | section "Skip-worktree bit" below for more information. | |
113 | ||
3240240f SB |
114 | -g:: |
115 | --again:: | |
0b444cdb | 116 | Runs 'git update-index' itself on the paths whose index |
83e77a25 JH |
117 | entries are different from those from the `HEAD` commit. |
118 | ||
060729dd MK |
119 | --unresolve:: |
120 | Restores the 'unmerged' or 'needs updating' state of a | |
121 | file during a merge if it was cleared by accident. | |
122 | ||
df6e1516 BL |
123 | --info-only:: |
124 | Do not create objects in the object database for all | |
125 | <file> arguments that follow this flag; just insert | |
5f3aa197 | 126 | their object IDs into the index. |
df6e1516 | 127 | |
2cf565c5 DG |
128 | --force-remove:: |
129 | Remove the file from the index even when the working directory | |
9b63f501 | 130 | still has such a file. (Implies --remove.) |
2cf565c5 DG |
131 | |
132 | --replace:: | |
133 | By default, when a file `path` exists in the index, | |
0b444cdb | 134 | 'git update-index' refuses an attempt to add `path/file`. |
2cf565c5 DG |
135 | Similarly if a file `path/file` exists, a file `path` |
136 | cannot be added. With --replace flag, existing entries | |
04c8ce9c | 137 | that conflict with the entry being added are |
2cf565c5 DG |
138 | automatically removed with warning messages. |
139 | ||
1f7f99de JH |
140 | --stdin:: |
141 | Instead of taking list of paths from the command line, | |
142 | read list of paths from the standard input. Paths are | |
143 | separated by LF (i.e. one path per line) by default. | |
144 | ||
14470c0d CS |
145 | --verbose:: |
146 | Report what is being added and removed from index. | |
147 | ||
69dec66b JH |
148 | --index-version <n>:: |
149 | Write the resulting index out in the named on-disk format version. | |
647d8794 NTND |
150 | Supported versions are 2, 3 and 4. The current default version is 2 |
151 | or 3, depending on whether extra features are used, such as | |
152 | `git add -N`. | |
153 | + | |
154 | Version 4 performs a simple pathname compression that reduces index | |
155 | size by 30%-50% on large repositories, which results in faster load | |
156 | time. Version 4 is relatively young (first released in in 1.8.0 in | |
157 | October 2012). Other Git implementations such as JGit and libgit2 | |
158 | may not support it yet. | |
69dec66b | 159 | |
1f7f99de | 160 | -z:: |
537497be BW |
161 | Only meaningful with `--stdin` or `--index-info`; paths are |
162 | separated with NUL character instead of LF. | |
1f7f99de | 163 | |
c18b80a0 NTND |
164 | --split-index:: |
165 | --no-split-index:: | |
b4601395 CC |
166 | Enable or disable split index mode. If split-index mode is |
167 | already enabled and `--split-index` is given again, all | |
168 | changes in $GIT_DIR/index are pushed back to the shared index | |
169 | file. | |
13c0e4c4 CC |
170 | + |
171 | These options take effect whatever the value of the `core.splitIndex` | |
172 | configuration variable (see linkgit:git-config[1]). But a warning is | |
173 | emitted when the change goes against the configured value, as the | |
174 | configured value will take effect next time the index is read and this | |
175 | will remove the intended effect of the option. | |
c18b80a0 | 176 | |
9e597241 NTND |
177 | --untracked-cache:: |
178 | --no-untracked-cache:: | |
435ec090 CC |
179 | Enable or disable untracked cache feature. Please use |
180 | `--test-untracked-cache` before enabling it. | |
181 | + | |
182 | These options take effect whatever the value of the `core.untrackedCache` | |
183 | configuration variable (see linkgit:git-config[1]). But a warning is | |
184 | emitted when the change goes against the configured value, as the | |
185 | configured value will take effect next time the index is read and this | |
186 | will remove the intended effect of the option. | |
9e597241 | 187 | |
eaab83d0 CC |
188 | --test-untracked-cache:: |
189 | Only perform tests on the working directory to make sure | |
190 | untracked cache can be used. You have to manually enable | |
435ec090 CC |
191 | untracked cache using `--untracked-cache` or |
192 | `--force-untracked-cache` or the `core.untrackedCache` | |
193 | configuration variable afterwards if you really want to use | |
194 | it. If a test fails the exit code is 1 and a message | |
195 | explains what is not working as needed, otherwise the exit | |
196 | code is 0 and OK is printed. | |
eaab83d0 | 197 | |
f64cb88d | 198 | --force-untracked-cache:: |
435ec090 CC |
199 | Same as `--untracked-cache`. Provided for backwards |
200 | compatibility with older versions of Git where | |
201 | `--untracked-cache` used to imply `--test-untracked-cache` but | |
202 | this option would enable the extension unconditionally. | |
f64cb88d | 203 | |
e994004f | 204 | \--:: |
2cf565c5 DG |
205 | Do not interpret any more arguments as options. |
206 | ||
207 | <file>:: | |
208 | Files to act on. | |
5773c9f2 | 209 | Note that files beginning with '.' are discarded. This includes |
a6080a0a | 210 | `./file` and `dir/./file`. If you don't want this, then use |
2cf565c5 DG |
211 | cleaner names. |
212 | The same applies to directories ending '/' and paths with '//' | |
213 | ||
214 | Using --refresh | |
215 | --------------- | |
bcf9626a | 216 | `--refresh` does not calculate a new sha1 file or bring the index |
2cf565c5 | 217 | up-to-date for mode/content changes. But what it *does* do is to |
5f3aa197 LS |
218 | "re-match" the stat information of a file with the index, so that you |
219 | can refresh the index for a file that hasn't been changed but where | |
2cf565c5 DG |
220 | the stat entry is out of date. |
221 | ||
0b444cdb | 222 | For example, you'd want to do this after doing a 'git read-tree', to link |
5f3aa197 | 223 | up the stat index details with the proper files. |
2cf565c5 | 224 | |
df6e1516 BL |
225 | Using --cacheinfo or --info-only |
226 | -------------------------------- | |
bcf9626a | 227 | `--cacheinfo` is used to register a file that is not in the |
df6e1516 BL |
228 | current working directory. This is useful for minimum-checkout |
229 | merging. | |
230 | ||
df8baa42 | 231 | To pretend you have a file with mode and sha1 at path, say: |
2cf565c5 | 232 | |
61f693bd | 233 | ---------------- |
7ac92f64 | 234 | $ git update-index --cacheinfo <mode>,<sha1>,<path> |
61f693bd | 235 | ---------------- |
2cf565c5 | 236 | |
bcf9626a | 237 | `--info-only` is used to register files without placing them in the object |
df6e1516 | 238 | database. This is useful for status-only repositories. |
2cf565c5 | 239 | |
bcf9626a MM |
240 | Both `--cacheinfo` and `--info-only` behave similarly: the index is updated |
241 | but the object database isn't. `--cacheinfo` is useful when the object is | |
242 | in the database but the file isn't available locally. `--info-only` is | |
df6e1516 BL |
243 | useful when the file is available, but you do not wish to update the |
244 | object database. | |
245 | ||
d23748a6 JH |
246 | |
247 | Using --index-info | |
248 | ------------------ | |
249 | ||
250 | `--index-info` is a more powerful mechanism that lets you feed | |
251 | multiple entry definitions from the standard input, and designed | |
252 | specifically for scripts. It can take inputs of three formats: | |
253 | ||
254 | . mode SP sha1 TAB path | |
255 | + | |
256 | The first format is what "git-apply --index-info" | |
257 | reports, and used to reconstruct a partial tree | |
258 | that is used for phony merge base tree when falling | |
259 | back on 3-way merge. | |
260 | ||
261 | . mode SP type SP sha1 TAB path | |
262 | + | |
0b444cdb | 263 | The second format is to stuff 'git ls-tree' output |
d23748a6 JH |
264 | into the index file. |
265 | ||
266 | . mode SP sha1 SP stage TAB path | |
267 | + | |
268 | This format is to put higher order stages into the | |
0b444cdb | 269 | index file and matches 'git ls-files --stage' output. |
d23748a6 JH |
270 | |
271 | To place a higher stage entry to the index, the path should | |
272 | first be removed by feeding a mode=0 entry for the path, and | |
273 | then feeding necessary input lines in the third format. | |
274 | ||
275 | For example, starting with this index: | |
276 | ||
277 | ------------ | |
278 | $ git ls-files -s | |
279 | 100644 8a1218a1024a212bb3db30becd860315f9f3ac52 0 frotz | |
280 | ------------ | |
281 | ||
282 | you can feed the following input to `--index-info`: | |
283 | ||
284 | ------------ | |
285 | $ git update-index --index-info | |
286 | 0 0000000000000000000000000000000000000000 frotz | |
287 | 100644 8a1218a1024a212bb3db30becd860315f9f3ac52 1 frotz | |
288 | 100755 8a1218a1024a212bb3db30becd860315f9f3ac52 2 frotz | |
289 | ------------ | |
290 | ||
291 | The first line of the input feeds 0 as the mode to remove the | |
d5fa1f1a | 292 | path; the SHA-1 does not matter as long as it is well formatted. |
d23748a6 JH |
293 | Then the second and third line feeds stage 1 and stage 2 entries |
294 | for that path. After the above, we would end up with this: | |
295 | ||
296 | ------------ | |
297 | $ git ls-files -s | |
298 | 100644 8a1218a1024a212bb3db30becd860315f9f3ac52 1 frotz | |
299 | 100755 8a1218a1024a212bb3db30becd860315f9f3ac52 2 frotz | |
300 | ------------ | |
301 | ||
302 | ||
bae777db JF |
303 | Using ``assume unchanged'' bit |
304 | ------------------------------ | |
f9666adf | 305 | |
2de9b711 | 306 | Many operations in Git depend on your filesystem to have an |
f9666adf JH |
307 | efficient `lstat(2)` implementation, so that `st_mtime` |
308 | information for working tree files can be cheaply checked to see | |
309 | if the file contents have changed from the version recorded in | |
310 | the index file. Unfortunately, some filesystems have | |
311 | inefficient `lstat(2)`. If your filesystem is one of them, you | |
312 | can set "assume unchanged" bit to paths you have not changed to | |
2de9b711 TA |
313 | cause Git not to do this check. Note that setting this bit on a |
314 | path does not mean Git will check the contents of the file to | |
315 | see if it has changed -- it makes Git to omit any checking and | |
f9666adf | 316 | assume it has *not* changed. When you make changes to working |
2de9b711 | 317 | tree files, you have to explicitly tell Git about it by dropping |
f9666adf JH |
318 | "assume unchanged" bit, either before or after you modify them. |
319 | ||
320 | In order to set "assume unchanged" bit, use `--assume-unchanged` | |
acd6d7e7 SN |
321 | option. To unset, use `--no-assume-unchanged`. To see which files |
322 | have the "assume unchanged" bit set, use `git ls-files -v` | |
323 | (see linkgit:git-ls-files[1]). | |
f9666adf JH |
324 | |
325 | The command looks at `core.ignorestat` configuration variable. When | |
b1889c36 | 326 | this is true, paths updated with `git update-index paths...` and |
2de9b711 | 327 | paths updated with other Git commands that update both index and |
0b444cdb TR |
328 | working tree (e.g. 'git apply --index', 'git checkout-index -u', |
329 | and 'git read-tree -u') are automatically marked as "assume | |
f9666adf | 330 | unchanged". Note that "assume unchanged" bit is *not* set if |
b1889c36 JN |
331 | `git update-index --refresh` finds the working tree file matches |
332 | the index (use `git update-index --really-refresh` if you want | |
f9666adf JH |
333 | to mark them as "assume unchanged"). |
334 | ||
335 | ||
df6e1516 BL |
336 | Examples |
337 | -------- | |
2cf565c5 DG |
338 | To update and refresh only the files already checked out: |
339 | ||
61f693bd | 340 | ---------------- |
b1889c36 | 341 | $ git checkout-index -n -f -a && git update-index --ignore-missing --refresh |
61f693bd | 342 | ---------------- |
2cf565c5 | 343 | |
48aeecdc SE |
344 | On an inefficient filesystem with `core.ignorestat` set:: |
345 | + | |
f9666adf | 346 | ------------ |
48aeecdc SE |
347 | $ git update-index --really-refresh <1> |
348 | $ git update-index --no-assume-unchanged foo.c <2> | |
349 | $ git diff --name-only <3> | |
f9666adf | 350 | $ edit foo.c |
48aeecdc | 351 | $ git diff --name-only <4> |
f9666adf | 352 | M foo.c |
48aeecdc SE |
353 | $ git update-index foo.c <5> |
354 | $ git diff --name-only <6> | |
f9666adf | 355 | $ edit foo.c |
48aeecdc SE |
356 | $ git diff --name-only <7> |
357 | $ git update-index --no-assume-unchanged foo.c <8> | |
358 | $ git diff --name-only <9> | |
f9666adf | 359 | M foo.c |
48aeecdc SE |
360 | ------------ |
361 | + | |
362 | <1> forces lstat(2) to set "assume unchanged" bits for paths that match index. | |
f9666adf JH |
363 | <2> mark the path to be edited. |
364 | <3> this does lstat(2) and finds index matches the path. | |
48aeecdc | 365 | <4> this does lstat(2) and finds index does *not* match the path. |
f9666adf JH |
366 | <5> registering the new version to index sets "assume unchanged" bit. |
367 | <6> and it is assumed unchanged. | |
368 | <7> even after you edit it. | |
369 | <8> you can tell about the change after the fact. | |
370 | <9> now it checks with lstat(2) and finds it has been changed. | |
f9666adf | 371 | |
2cf565c5 | 372 | |
44a36913 NTND |
373 | Skip-worktree bit |
374 | ----------------- | |
375 | ||
376 | Skip-worktree bit can be defined in one (long) sentence: When reading | |
377 | an entry, if it is marked as skip-worktree, then Git pretends its | |
378 | working directory version is up to date and read the index version | |
379 | instead. | |
380 | ||
381 | To elaborate, "reading" means checking for file existence, reading | |
382 | file attributes or file content. The working directory version may be | |
383 | present or absent. If present, its content may match against the index | |
384 | version or not. Writing is not affected by this bit, content safety | |
385 | is still first priority. Note that Git _can_ update working directory | |
386 | file, that is marked skip-worktree, if it is safe to do so (i.e. | |
387 | working directory version matches index version) | |
388 | ||
389 | Although this bit looks similar to assume-unchanged bit, its goal is | |
390 | different from assume-unchanged bit's. Skip-worktree also takes | |
391 | precedence over assume-unchanged bit when both are set. | |
392 | ||
b4601395 CC |
393 | Split index |
394 | ----------- | |
395 | ||
396 | This mode is designed for repositories with very large indexes, and | |
397 | aims at reducing the time it takes to repeatedly write these indexes. | |
398 | ||
399 | In this mode, the index is split into two files, $GIT_DIR/index and | |
400 | $GIT_DIR/sharedindex.<SHA-1>. Changes are accumulated in | |
401 | $GIT_DIR/index, the split index, while the shared index file contains | |
402 | all index entries and stays unchanged. | |
403 | ||
404 | All changes in the split index are pushed back to the shared index | |
405 | file when the number of entries in the split index reaches a level | |
406 | specified by the splitIndex.maxPercentChange config variable (see | |
407 | linkgit:git-config[1]). | |
408 | ||
409 | Each time a new shared index file is created, the old shared index | |
410 | files are deleted if their modification time is older than what is | |
411 | specified by the splitIndex.sharedIndexExpire config variable (see | |
412 | linkgit:git-config[1]). | |
413 | ||
414 | To avoid deleting a shared index file that is still used, its | |
415 | modification time is updated to the current time everytime a new split | |
416 | index based on the shared index file is either created or read from. | |
417 | ||
435ec090 CC |
418 | Untracked cache |
419 | --------------- | |
420 | ||
421 | This cache is meant to speed up commands that involve determining | |
422 | untracked files such as `git status`. | |
423 | ||
424 | This feature works by recording the mtime of the working tree | |
425 | directories and then omitting reading directories and stat calls | |
426 | against files in those directories whose mtime hasn't changed. For | |
427 | this to work the underlying operating system and file system must | |
428 | change the `st_mtime` field of directories if files in the directory | |
429 | are added, modified or deleted. | |
430 | ||
431 | You can test whether the filesystem supports that with the | |
432 | `--test-untracked-cache` option. The `--untracked-cache` option used | |
433 | to implicitly perform that test in older versions of Git, but that's | |
434 | no longer the case. | |
435 | ||
436 | If you want to enable (or disable) this feature, it is easier to use | |
437 | the `core.untrackedCache` configuration variable (see | |
438 | linkgit:git-config[1]) than using the `--untracked-cache` option to | |
439 | `git update-index` in each repository, especially if you want to do so | |
440 | across all repositories you use, because you can set the configuration | |
441 | variable to `true` (or `false`) in your `$HOME/.gitconfig` just once | |
442 | and have it affect all repositories you touch. | |
443 | ||
444 | When the `core.untrackedCache` configuration variable is changed, the | |
445 | untracked cache is added to or removed from the index the next time a | |
446 | command reads the index; while when `--[no-|force-]untracked-cache` | |
447 | are used, the untracked cache is immediately added to or removed from | |
448 | the index. | |
44a36913 | 449 | |
5773c9f2 JH |
450 | Configuration |
451 | ------------- | |
452 | ||
453 | The command honors `core.filemode` configuration variable. If | |
466d1f15 | 454 | your repository is on a filesystem whose executable bits are |
5162e697 | 455 | unreliable, this should be set to 'false' (see linkgit:git-config[1]). |
61f693bd JL |
456 | This causes the command to ignore differences in file modes recorded |
457 | in the index and the file mode on the filesystem if they differ only on | |
5773c9f2 | 458 | executable bit. On such an unfortunate filesystem, you may |
0b444cdb | 459 | need to use 'git update-index --chmod='. |
5773c9f2 | 460 | |
78a8d641 | 461 | Quite similarly, if `core.symlinks` configuration variable is set |
5162e697 | 462 | to 'false' (see linkgit:git-config[1]), symbolic links are checked out |
78a8d641 JS |
463 | as plain files, and this command does not modify a recorded file mode |
464 | from symbolic link to regular file. | |
465 | ||
f9666adf JH |
466 | The command looks at `core.ignorestat` configuration variable. See |
467 | 'Using "assume unchanged" bit' section above. | |
468 | ||
1ce4790b AR |
469 | The command also looks at `core.trustctime` configuration variable. |
470 | It can be useful when the inode change time is regularly modified by | |
471 | something outside Git (file system crawlers and backup systems use | |
472 | ctime for marking files processed) (see linkgit:git-config[1]). | |
473 | ||
435ec090 CC |
474 | The untracked cache extension can be enabled by the |
475 | `core.untrackedCache` configuration variable (see | |
476 | linkgit:git-config[1]). | |
61f693bd | 477 | |
56ae8df5 | 478 | SEE ALSO |
61f693bd | 479 | -------- |
5162e697 | 480 | linkgit:git-config[1], |
acd6d7e7 SN |
481 | linkgit:git-add[1], |
482 | linkgit:git-ls-files[1] | |
61f693bd | 483 | |
2cf565c5 DG |
484 | GIT |
485 | --- | |
9e1f0a85 | 486 | Part of the linkgit:git[1] suite |