git-update-index.txt 10.1 KB
Newer Older
Junio C Hamano's avatar
Junio C Hamano committed
1
git-update-index(1)
2 3 4 5
===================

NAME
----
Junio C Hamano's avatar
Junio C Hamano committed
6
git-update-index - Modifies the index or directory cache
7 8 9 10


SYNOPSIS
--------
11
[verse]
Junio C Hamano's avatar
Junio C Hamano committed
12
'git-update-index'
13 14
	     [--add] [--remove | --force-remove] [--replace]
	     [--refresh] [-q] [--unmerged] [--ignore-missing]
15
	     [--cacheinfo <mode> <object> <file>]\*
Junio C Hamano's avatar
Junio C Hamano committed
16
	     [--chmod=(+|-)x]
17
	     [--assume-unchanged | --no-assume-unchanged]
18
	     [--really-refresh] [--unresolve]
19 20 21
	     [--info-only] [--index-info]
	     [-z] [--stdin]
	     [--verbose]
22 23 24 25 26
	     [--] [<file>]\*

DESCRIPTION
-----------
Modifies the index or directory cache. Each file mentioned is updated
27
into the index and any 'unmerged' or 'needs updating' state is
28 29
cleared.

Junio C Hamano's avatar
Junio C Hamano committed
30
The way "git-update-index" handles files it is told about can be modified
31 32 33 34 35
using the various options:

OPTIONS
-------
--add::
36
	If a specified file isn't in the index already then it's
37 38 39 40
	added.
	Default behaviour is to ignore new files.

--remove::
41
	If a specified file is in the index but is missing then it's
42 43 44 45
	removed.
	Default behaviour is to ignore removed file.

--refresh::
46
	Looks at the current index and checks to see if merges or
47 48
	updates are needed by checking stat() information.

49
-q::
50
        Quiet.  If --refresh finds that the index needs an update, the
51 52 53 54
        default behavior is to error out.  This option makes
        git-update-index continue anyway.

--unmerged::
55
        If --refresh finds unmerged changes in the index, the default
56 57 58
        behavior is to error out.  This option makes git-update-index 
        continue anyway.

59 60 61 62
--ignore-missing::
	Ignores missing files during a --refresh

--cacheinfo <mode> <object> <path>::
63
	Directly insert the specified info into the index.
64
	
65
--index-info::
Nikolai Weibull's avatar
Nikolai Weibull committed
66
        Read index information from stdin.
67 68 69 70

--chmod=(+|-)x::
        Set the execute permissions on the updated files.        

71 72 73 74 75 76 77 78 79 80 81 82
--assume-unchanged, --no-assume-unchanged::
	When these flags are specified, the object name recorded
	for the paths are not updated.  Instead, these options
	sets and unsets the "assume unchanged" bit for the
	paths.  When the "assume unchanged" bit is on, git stops
	checking the working tree files for possible
	modifications, so you need to manually unset the bit to
	tell git when you change the working tree file. This is
	sometimes helpful when working with a big project on a
	filesystem that has very slow lstat(2) system call
	(e.g. cifs).

83 84 85 86
--unresolve::
	Restores the 'unmerged' or 'needs updating' state of a
	file during a merge if it was cleared by accident.

87 88 89
--info-only::
	Do not create objects in the object database for all
	<file> arguments that follow this flag; just insert
90
	their object IDs into the index.
91

92 93
--force-remove::
	Remove the file from the index even when the working directory
94
	still has such a file. (Implies --remove.)
95 96 97

--replace::
	By default, when a file `path` exists in the index,
Junio C Hamano's avatar
Junio C Hamano committed
98
	git-update-index refuses an attempt to add `path/file`.
99 100 101 102 103
	Similarly if a file `path/file` exists, a file `path`
	cannot be added.  With --replace flag, existing entries
	that conflicts with the entry being added are
	automatically removed with warning messages.

104 105 106 107 108
--stdin::
	Instead of taking list of paths from the command line,
	read list of paths from the standard input.  Paths are
	separated by LF (i.e. one path per line) by default.

109 110 111
--verbose::
        Report what is being added and removed from index.

112 113 114 115
-z::
	Only meaningful with `--stdin`; paths are separated with
	NUL character instead of LF.

116 117 118 119 120
--::
	Do not interpret any more arguments as options.

<file>::
	Files to act on.
Junio C Hamano's avatar
Junio C Hamano committed
121
	Note that files beginning with '.' are discarded. This includes
122 123 124 125 126 127
	`./file` and `dir/./file`. If you don't want this, then use	
	cleaner names.
	The same applies to directories ending '/' and paths with '//'

Using --refresh
---------------
128
'--refresh' does not calculate a new sha1 file or bring the index
129
up-to-date for mode/content changes. But what it *does* do is to
130 131
"re-match" the stat information of a file with the index, so that you
can refresh the index for a file that hasn't been changed but where
132 133 134
the stat entry is out of date.

For example, you'd want to do this after doing a "git-read-tree", to link
135
up the stat index details with the proper files.
136

137 138 139 140 141 142
Using --cacheinfo or --info-only
--------------------------------
'--cacheinfo' is used to register a file that is not in the
current working directory.  This is useful for minimum-checkout
merging.

143
To pretend you have a file with mode and sha1 at path, say:
144

145 146 147
----------------
$ git-update-index --cacheinfo mode sha1 path
----------------
148

149 150
'--info-only' is used to register files without placing them in the object
database.  This is useful for status-only repositories.
151

152 153 154 155 156 157
Both '--cacheinfo' and '--info-only' behave similarly: the index is updated
but the object database isn't.  '--cacheinfo' is useful when the object is
in the database but the file isn't available locally.  '--info-only' is
useful when the file is available, but you do not wish to update the
object database.

158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214

Using --index-info
------------------

`--index-info` is a more powerful mechanism that lets you feed
multiple entry definitions from the standard input, and designed
specifically for scripts.  It can take inputs of three formats:

    . mode         SP sha1          TAB path
+
The first format is what "git-apply --index-info"
reports, and used to reconstruct a partial tree
that is used for phony merge base tree when falling
back on 3-way merge.

    . mode SP type SP sha1          TAB path
+
The second format is to stuff git-ls-tree output
into the index file.

    . mode         SP sha1 SP stage TAB path
+
This format is to put higher order stages into the
index file and matches git-ls-files --stage output.

To place a higher stage entry to the index, the path should
first be removed by feeding a mode=0 entry for the path, and
then feeding necessary input lines in the third format.

For example, starting with this index:

------------
$ git ls-files -s
100644 8a1218a1024a212bb3db30becd860315f9f3ac52 0       frotz
------------

you can feed the following input to `--index-info`:

------------
$ git update-index --index-info
0 0000000000000000000000000000000000000000	frotz
100644 8a1218a1024a212bb3db30becd860315f9f3ac52 1	frotz
100755 8a1218a1024a212bb3db30becd860315f9f3ac52 2	frotz
------------

The first line of the input feeds 0 as the mode to remove the
path; the SHA1 does not matter as long as it is well formatted.
Then the second and third line feeds stage 1 and stage 2 entries
for that path.  After the above, we would end up with this:

------------
$ git ls-files -s
100644 8a1218a1024a212bb3db30becd860315f9f3ac52 1	frotz
100755 8a1218a1024a212bb3db30becd860315f9f3ac52 2	frotz
------------


215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245
Using "assume unchanged" bit
----------------------------

Many operations in git depend on your filesystem to have an
efficient `lstat(2)` implementation, so that `st_mtime`
information for working tree files can be cheaply checked to see
if the file contents have changed from the version recorded in
the index file.  Unfortunately, some filesystems have
inefficient `lstat(2)`.  If your filesystem is one of them, you
can set "assume unchanged" bit to paths you have not changed to
cause git not to do this check.  Note that setting this bit on a
path does not mean git will check the contents of the file to
see if it has changed -- it makes git to omit any checking and
assume it has *not* changed.  When you make changes to working
tree files, you have to explicitly tell git about it by dropping
"assume unchanged" bit, either before or after you modify them.

In order to set "assume unchanged" bit, use `--assume-unchanged`
option.  To unset, use `--no-assume-unchanged`.

The command looks at `core.ignorestat` configuration variable.  When
this is true, paths updated with `git-update-index paths...` and
paths updated with other git commands that update both index and
working tree (e.g. `git-apply --index`, `git-checkout-index -u`,
and `git-read-tree -u`) are automatically marked as "assume
unchanged".  Note that "assume unchanged" bit is *not* set if
`git-update-index --refresh` finds the working tree file matches
the index (use `git-update-index --really-refresh` if you want
to mark them as "assume unchanged").


246 247
Examples
--------
248 249
To update and refresh only the files already checked out:

250 251 252
----------------
$ git-checkout-index -n -f -a && git-update-index --ignore-missing --refresh
----------------
253

254 255
On an inefficient filesystem with `core.ignorestat` set::
+
256
------------
257 258 259
$ git update-index --really-refresh              <1>
$ git update-index --no-assume-unchanged foo.c   <2>
$ git diff --name-only                           <3>
260
$ edit foo.c
261
$ git diff --name-only                           <4>
262
M foo.c
263 264
$ git update-index foo.c                         <5>
$ git diff --name-only                           <6>
265
$ edit foo.c
266 267 268
$ git diff --name-only                           <7>
$ git update-index --no-assume-unchanged foo.c   <8>
$ git diff --name-only                           <9>
269
M foo.c
270 271 272
------------
+
<1> forces lstat(2) to set "assume unchanged" bits for paths that match index.
273 274
<2> mark the path to be edited.
<3> this does lstat(2) and finds index matches the path.
275
<4> this does lstat(2) and finds index does *not* match the path.
276 277 278 279 280 281
<5> registering the new version to index sets "assume unchanged" bit.
<6> and it is assumed unchanged.
<7> even after you edit it.
<8> you can tell about the change after the fact.
<9> now it checks with lstat(2) and finds it has been changed.

282

Junio C Hamano's avatar
Junio C Hamano committed
283 284 285 286 287
Configuration
-------------

The command honors `core.filemode` configuration variable.  If
your repository is on an filesystem whose executable bits are
288 289 290
unreliable, this should be set to 'false' (see gitlink:git-repo-config[1]).
This causes the command to ignore differences in file modes recorded
in the index and the file mode on the filesystem if they differ only on
Junio C Hamano's avatar
Junio C Hamano committed
291 292 293
executable bit.   On such an unfortunate filesystem, you may
need to use `git-update-index --chmod=`.

294 295 296
The command looks at `core.ignorestat` configuration variable.  See
'Using "assume unchanged" bit' section above.

297 298 299 300 301 302

See Also
--------
gitlink:git-repo-config[1]


303 304 305 306 307 308 309 310 311 312
Author
------
Written by Linus Torvalds <[email protected]>

Documentation
--------------
Documentation by David Greaves, Junio C Hamano and the git-list <[email protected]>.

GIT
---
313
Part of the gitlink:git[7] suite
314