]>
Commit | Line | Data |
---|---|---|
9e1f0a85 | 1 | git(1) |
2cf565c5 | 2 | ====== |
2cf565c5 DG |
3 | |
4 | NAME | |
5 | ---- | |
6 | git - the stupid content tracker | |
7 | ||
8 | ||
9 | SYNOPSIS | |
10 | -------- | |
8b70004b | 11 | [verse] |
89a56bfb | 12 | 'git' [--version] [--exec-path[=GIT_EXEC_PATH]] [--html-path] |
463a849d | 13 | [-p|--paginate|--no-pager] |
892c41b9 ML |
14 | [--bare] [--git-dir=GIT_DIR] [--work-tree=GIT_WORK_TREE] |
15 | [--help] COMMAND [ARGS] | |
2cf565c5 DG |
16 | |
17 | DESCRIPTION | |
18 | ----------- | |
23091e95 BF |
19 | Git is a fast, scalable, distributed revision control system with an |
20 | unusually rich command set that provides both high-level operations | |
21 | and full access to internals. | |
22 | ||
6998e4db | 23 | See linkgit:gittutorial[7] to get started, then see |
23091e95 BF |
24 | link:everyday.html[Everyday Git] for a useful minimum set of commands, and |
25 | "man git-commandname" for documentation of each command. CVS users may | |
6998e4db JN |
26 | also want to read linkgit:gitcvs-migration[7]. See |
27 | the link:user-manual.html[Git User's Manual] for a more in-depth | |
a1dc34fa | 28 | introduction. |
cb22bc44 | 29 | |
4514ad4f | 30 | The COMMAND is either a name of a Git command (see below) or an alias |
5162e697 | 31 | as defined in the configuration file (see linkgit:git-config[1]). |
4514ad4f | 32 | |
34b604af JA |
33 | Formatted and hyperlinked version of the latest git |
34 | documentation can be viewed at | |
35 | `http://www.kernel.org/pub/software/scm/git/docs/`. | |
36 | ||
26cfcfbf JH |
37 | ifdef::stalenotes[] |
38 | [NOTE] | |
39 | ============ | |
26cfcfbf | 40 | |
2ff3f61a JH |
41 | You are reading the documentation for the latest (possibly |
42 | unreleased) version of git, that is available from 'master' | |
43 | branch of the `git.git` repository. | |
44 | Documentation for older releases are available here: | |
43a8e4fe | 45 | |
441b40d8 | 46 | * link:v1.6.3.4/git.html[documentation for release 1.6.3.4] |
6096d759 JH |
47 | |
48 | * release notes for | |
441b40d8 | 49 | link:RelNotes-1.6.3.4.txt[1.6.3.4], |
e16a4779 | 50 | link:RelNotes-1.6.3.3.txt[1.6.3.3], |
6096d759 JH |
51 | link:RelNotes-1.6.3.2.txt[1.6.3.2], |
52 | link:RelNotes-1.6.3.1.txt[1.6.3.1], | |
53 | link:RelNotes-1.6.3.txt[1.6.3]. | |
a95148de JH |
54 | |
55 | * release notes for | |
f01f1099 JH |
56 | link:RelNotes-1.6.2.5.txt[1.6.2.5], |
57 | link:RelNotes-1.6.2.4.txt[1.6.2.4], | |
c965c029 | 58 | link:RelNotes-1.6.2.3.txt[1.6.2.3], |
54a47493 | 59 | link:RelNotes-1.6.2.2.txt[1.6.2.2], |
de769780 | 60 | link:RelNotes-1.6.2.1.txt[1.6.2.1], |
a95148de JH |
61 | link:RelNotes-1.6.2.txt[1.6.2]. |
62 | ||
621f1b4b | 63 | * link:v1.6.1.3/git.html[documentation for release 1.6.1.3] |
8104ebfe JH |
64 | |
65 | * release notes for | |
621f1b4b JH |
66 | link:RelNotes-1.6.1.3.txt[1.6.1.3], |
67 | link:RelNotes-1.6.1.2.txt[1.6.1.2], | |
c42b1ad9 | 68 | link:RelNotes-1.6.1.1.txt[1.6.1.1], |
8104ebfe JH |
69 | link:RelNotes-1.6.1.txt[1.6.1]. |
70 | ||
efe05b01 | 71 | * link:v1.6.0.6/git.html[documentation for release 1.6.0.6] |
ea02eef0 JH |
72 | |
73 | * release notes for | |
efe05b01 | 74 | link:RelNotes-1.6.0.6.txt[1.6.0.6], |
f371d3ea | 75 | link:RelNotes-1.6.0.5.txt[1.6.0.5], |
171d7661 JH |
76 | link:RelNotes-1.6.0.4.txt[1.6.0.4], |
77 | link:RelNotes-1.6.0.3.txt[1.6.0.3], | |
97a7a82f JH |
78 | link:RelNotes-1.6.0.2.txt[1.6.0.2], |
79 | link:RelNotes-1.6.0.1.txt[1.6.0.1], | |
ea02eef0 JH |
80 | link:RelNotes-1.6.0.txt[1.6.0]. |
81 | ||
efe05b01 | 82 | * link:v1.5.6.6/git.html[documentation for release 1.5.6.6] |
e449f105 JH |
83 | |
84 | * release notes for | |
efe05b01 | 85 | link:RelNotes-1.5.6.6.txt[1.5.6.6], |
781c1834 | 86 | link:RelNotes-1.5.6.5.txt[1.5.6.5], |
09651dd8 JH |
87 | link:RelNotes-1.5.6.4.txt[1.5.6.4], |
88 | link:RelNotes-1.5.6.3.txt[1.5.6.3], | |
89 | link:RelNotes-1.5.6.2.txt[1.5.6.2], | |
90 | link:RelNotes-1.5.6.1.txt[1.5.6.1], | |
e636106c | 91 | link:RelNotes-1.5.6.txt[1.5.6]. |
e449f105 | 92 | |
efe05b01 | 93 | * link:v1.5.5.6/git.html[documentation for release 1.5.5.6] |
1d2375dd JH |
94 | |
95 | * release notes for | |
efe05b01 JH |
96 | link:RelNotes-1.5.5.6.txt[1.5.5.6], |
97 | link:RelNotes-1.5.5.5.txt[1.5.5.5], | |
7064ca51 | 98 | link:RelNotes-1.5.5.4.txt[1.5.5.4], |
28bc3022 | 99 | link:RelNotes-1.5.5.3.txt[1.5.5.3], |
2d3922dc | 100 | link:RelNotes-1.5.5.2.txt[1.5.5.2], |
66aaa2fc | 101 | link:RelNotes-1.5.5.1.txt[1.5.5.1], |
1d2375dd JH |
102 | link:RelNotes-1.5.5.txt[1.5.5]. |
103 | ||
efe05b01 | 104 | * link:v1.5.4.7/git.html[documentation for release 1.5.4.7] |
6ce8e44a JH |
105 | |
106 | * release notes for | |
efe05b01 JH |
107 | link:RelNotes-1.5.4.7.txt[1.5.4.7], |
108 | link:RelNotes-1.5.4.6.txt[1.5.4.6], | |
803d5158 | 109 | link:RelNotes-1.5.4.5.txt[1.5.4.5], |
ad416ed4 | 110 | link:RelNotes-1.5.4.4.txt[1.5.4.4], |
923d44ae | 111 | link:RelNotes-1.5.4.3.txt[1.5.4.3], |
cf5c51ef | 112 | link:RelNotes-1.5.4.2.txt[1.5.4.2], |
ecb879f8 | 113 | link:RelNotes-1.5.4.1.txt[1.5.4.1], |
6ce8e44a JH |
114 | link:RelNotes-1.5.4.txt[1.5.4]. |
115 | ||
e708af6e | 116 | * link:v1.5.3.8/git.html[documentation for release 1.5.3.8] |
5587cac2 JH |
117 | |
118 | * release notes for | |
e708af6e | 119 | link:RelNotes-1.5.3.8.txt[1.5.3.8], |
b52e985a | 120 | link:RelNotes-1.5.3.7.txt[1.5.3.7], |
4a44b9ea | 121 | link:RelNotes-1.5.3.6.txt[1.5.3.6], |
afc05f9f | 122 | link:RelNotes-1.5.3.5.txt[1.5.3.5], |
58ba4f6a | 123 | link:RelNotes-1.5.3.4.txt[1.5.3.4], |
326df26d | 124 | link:RelNotes-1.5.3.3.txt[1.5.3.3], |
077d6f72 | 125 | link:RelNotes-1.5.3.2.txt[1.5.3.2], |
8d863c98 JH |
126 | link:RelNotes-1.5.3.1.txt[1.5.3.1], |
127 | link:RelNotes-1.5.3.txt[1.5.3]. | |
b6e4db6a | 128 | |
e636106c JH |
129 | * link:v1.5.2.5/git.html[documentation for release 1.5.2.5] |
130 | ||
aba170cd | 131 | * release notes for |
da899deb | 132 | link:RelNotes-1.5.2.5.txt[1.5.2.5], |
baafd6e7 | 133 | link:RelNotes-1.5.2.4.txt[1.5.2.4], |
444649e5 | 134 | link:RelNotes-1.5.2.3.txt[1.5.2.3], |
3e48af38 JH |
135 | link:RelNotes-1.5.2.2.txt[1.5.2.2], |
136 | link:RelNotes-1.5.2.1.txt[1.5.2.1], | |
aba170cd JH |
137 | link:RelNotes-1.5.2.txt[1.5.2]. |
138 | ||
139 | * link:v1.5.1.6/git.html[documentation for release 1.5.1.6] | |
140 | ||
141 | * release notes for | |
142 | link:RelNotes-1.5.1.6.txt[1.5.1.6], | |
143 | link:RelNotes-1.5.1.5.txt[1.5.1.5], | |
2ff3f61a JH |
144 | link:RelNotes-1.5.1.4.txt[1.5.1.4], |
145 | link:RelNotes-1.5.1.3.txt[1.5.1.3], | |
146 | link:RelNotes-1.5.1.2.txt[1.5.1.2], | |
147 | link:RelNotes-1.5.1.1.txt[1.5.1.1], | |
148 | link:RelNotes-1.5.1.txt[1.5.1]. | |
149 | ||
150 | * link:v1.5.0.7/git.html[documentation for release 1.5.0.7] | |
151 | ||
aba170cd JH |
152 | * release notes for |
153 | link:RelNotes-1.5.0.7.txt[1.5.0.7], | |
2ff3f61a JH |
154 | link:RelNotes-1.5.0.6.txt[1.5.0.6], |
155 | link:RelNotes-1.5.0.5.txt[1.5.0.5], | |
156 | link:RelNotes-1.5.0.3.txt[1.5.0.3], | |
157 | link:RelNotes-1.5.0.2.txt[1.5.0.2], | |
158 | link:RelNotes-1.5.0.1.txt[1.5.0.1], | |
159 | link:RelNotes-1.5.0.txt[1.5.0]. | |
160 | ||
161 | * documentation for release link:v1.4.4.4/git.html[1.4.4.4], | |
162 | link:v1.3.3/git.html[1.3.3], | |
163 | link:v1.2.6/git.html[1.2.6], | |
164 | link:v1.0.13/git.html[1.0.13]. | |
26cfcfbf JH |
165 | |
166 | ============ | |
167 | ||
168 | endif::stalenotes[] | |
169 | ||
cb22bc44 AE |
170 | OPTIONS |
171 | ------- | |
172 | --version:: | |
a87cd02c | 173 | Prints the git suite version that the 'git' program came from. |
cb22bc44 AE |
174 | |
175 | --help:: | |
a87cd02c | 176 | Prints the synopsis and a list of the most commonly used |
0f6f195b CC |
177 | commands. If the option '--all' or '-a' is given then all |
178 | available commands are printed. If a git command is named this | |
179 | option will bring up the manual page for that command. | |
45533d26 CC |
180 | + |
181 | Other options are available to control how the manual page is | |
5162e697 | 182 | displayed. See linkgit:git-help[1] for more information, |
db5d6666 JN |
183 | because `git --help ...` is converted internally into `git |
184 | help ...`. | |
cb22bc44 AE |
185 | |
186 | --exec-path:: | |
a87cd02c | 187 | Path to wherever your core git programs are installed. |
cb22bc44 | 188 | This can also be controlled by setting the GIT_EXEC_PATH |
56992f76 | 189 | environment variable. If no path is given, 'git' will print |
cb22bc44 AE |
190 | the current setting and then exit. |
191 | ||
89a56bfb MH |
192 | --html-path:: |
193 | Print the path to wherever your git HTML documentation is installed | |
194 | and exit. | |
195 | ||
3240240f SB |
196 | -p:: |
197 | --paginate:: | |
6acbcb92 JS |
198 | Pipe all output into 'less' (or if set, $PAGER). |
199 | ||
463a849d MM |
200 | --no-pager:: |
201 | Do not pipe git output into a pager. | |
202 | ||
6acbcb92 JS |
203 | --git-dir=<path>:: |
204 | Set the path to the repository. This can also be controlled by | |
302cc11a LY |
205 | setting the GIT_DIR environment variable. It can be an absolute |
206 | path or relative path to current working directory. | |
6acbcb92 | 207 | |
892c41b9 ML |
208 | --work-tree=<path>:: |
209 | Set the path to the working tree. The value will not be | |
210 | used in combination with repositories found automatically in | |
211 | a .git directory (i.e. $GIT_DIR is not set). | |
212 | This can also be controlled by setting the GIT_WORK_TREE | |
213 | environment variable and the core.worktree configuration | |
302cc11a LY |
214 | variable. It can be an absolute path or relative path to |
215 | the directory specified by --git-dir or GIT_DIR. | |
216 | Note: If --git-dir or GIT_DIR are specified but none of | |
217 | --work-tree, GIT_WORK_TREE and core.worktree is specified, | |
218 | the current working directory is regarded as the top directory | |
219 | of your working tree. | |
892c41b9 | 220 | |
6acbcb92 | 221 | --bare:: |
9277d602 JH |
222 | Treat the repository as a bare repository. If GIT_DIR |
223 | environment is not set, it is set to the current working | |
224 | directory. | |
225 | ||
9755afbd | 226 | |
23091e95 BF |
227 | FURTHER DOCUMENTATION |
228 | --------------------- | |
9755afbd | 229 | |
23091e95 BF |
230 | See the references above to get started using git. The following is |
231 | probably more detail than necessary for a first-time user. | |
8db9307c | 232 | |
40dac517 | 233 | The link:user-manual.html#git-concepts[git concepts chapter of the |
6998e4db | 234 | user-manual] and linkgit:gitcore-tutorial[7] both provide |
40dac517 | 235 | introductions to the underlying git architecture. |
e6fc2346 | 236 | |
801a011d TR |
237 | See linkgit:gitworkflows[7] for an overview of recommended workflows. |
238 | ||
23091e95 BF |
239 | See also the link:howto-index.html[howto] documents for some useful |
240 | examples. | |
9755afbd | 241 | |
6998e4db JN |
242 | The internals are documented in the |
243 | link:technical/api-index.html[GIT API documentation]. | |
530e741c | 244 | |
23091e95 BF |
245 | GIT COMMANDS |
246 | ------------ | |
9755afbd | 247 | |
23091e95 BF |
248 | We divide git into high level ("porcelain") commands and low level |
249 | ("plumbing") commands. | |
8b15e2fb | 250 | |
23091e95 BF |
251 | High-level commands (porcelain) |
252 | ------------------------------- | |
253 | ||
254 | We separate the porcelain commands into the main commands and some | |
255 | ancillary user utilities. | |
256 | ||
257 | Main porcelain commands | |
258 | ~~~~~~~~~~~~~~~~~~~~~~~ | |
905197de | 259 | |
377e8139 | 260 | include::cmds-mainporcelain.txt[] |
e31bb3bb | 261 | |
90933efb | 262 | Ancillary Commands |
23091e95 | 263 | ~~~~~~~~~~~~~~~~~~ |
2f2de9b4 JH |
264 | Manipulators: |
265 | ||
377e8139 | 266 | include::cmds-ancillarymanipulators.txt[] |
204ee6a9 | 267 | |
90933efb | 268 | Interrogators: |
204ee6a9 | 269 | |
377e8139 | 270 | include::cmds-ancillaryinterrogators.txt[] |
7fc9d69f | 271 | |
89bf2077 JH |
272 | |
273 | Interacting with Others | |
274 | ~~~~~~~~~~~~~~~~~~~~~~~ | |
275 | ||
276 | These commands are to interact with foreign SCM and with other | |
277 | people via patch over e-mail. | |
278 | ||
279 | include::cmds-foreignscminterface.txt[] | |
280 | ||
281 | ||
b1f33d62 RR |
282 | Low-level commands (plumbing) |
283 | ----------------------------- | |
284 | ||
285 | Although git includes its | |
286 | own porcelain layer, its low-level commands are sufficient to support | |
287 | development of alternative porcelains. Developers of such porcelains | |
5162e697 DM |
288 | might start by reading about linkgit:git-update-index[1] and |
289 | linkgit:git-read-tree[1]. | |
b1f33d62 | 290 | |
89bf2077 JH |
291 | The interface (input, output, set of options and the semantics) |
292 | to these low-level commands are meant to be a lot more stable | |
293 | than Porcelain level commands, because these commands are | |
294 | primarily for scripted use. The interface to Porcelain commands | |
295 | on the other hand are subject to change in order to improve the | |
296 | end user experience. | |
297 | ||
298 | The following description divides | |
299 | the low-level commands into commands that manipulate objects (in | |
b1f33d62 RR |
300 | the repository, index, and working tree), commands that interrogate and |
301 | compare objects, and commands that move objects and references between | |
302 | repositories. | |
303 | ||
89bf2077 | 304 | |
b1f33d62 RR |
305 | Manipulation commands |
306 | ~~~~~~~~~~~~~~~~~~~~~ | |
b1f33d62 | 307 | |
377e8139 | 308 | include::cmds-plumbingmanipulators.txt[] |
b1f33d62 RR |
309 | |
310 | ||
311 | Interrogation commands | |
312 | ~~~~~~~~~~~~~~~~~~~~~~ | |
313 | ||
377e8139 | 314 | include::cmds-plumbinginterrogators.txt[] |
b1f33d62 RR |
315 | |
316 | In general, the interrogate commands do not touch the files in | |
317 | the working tree. | |
318 | ||
319 | ||
320 | Synching repositories | |
321 | ~~~~~~~~~~~~~~~~~~~~~ | |
322 | ||
377e8139 | 323 | include::cmds-synchingrepositories.txt[] |
b1f33d62 | 324 | |
89bf2077 JH |
325 | The following are helper programs used by the above; end users |
326 | typically do not use them directly. | |
327 | ||
328 | include::cmds-synchelpers.txt[] | |
329 | ||
330 | ||
331 | Internal helper commands | |
332 | ~~~~~~~~~~~~~~~~~~~~~~~~ | |
333 | ||
334 | These are internal helper commands used by other commands; end | |
335 | users typically do not use them directly. | |
336 | ||
337 | include::cmds-purehelpers.txt[] | |
338 | ||
b1f33d62 | 339 | |
5773c9f2 JH |
340 | Configuration Mechanism |
341 | ----------------------- | |
342 | ||
2fa090b6 | 343 | Starting from 0.99.9 (actually mid 0.99.8.GIT), `.git/config` file |
5773c9f2 | 344 | is used to hold per-repository configuration options. It is a |
addf88e4 | 345 | simple text file modeled after `.ini` format familiar to some |
5773c9f2 JH |
346 | people. Here is an example: |
347 | ||
348 | ------------ | |
349 | # | |
2fa090b6 | 350 | # A '#' or ';' character indicates a comment. |
5773c9f2 JH |
351 | # |
352 | ||
353 | ; core variables | |
354 | [core] | |
355 | ; Don't trust file modes | |
356 | filemode = false | |
357 | ||
358 | ; user identity | |
359 | [user] | |
360 | name = "Junio C Hamano" | |
361 | email = "junkio@twinsun.com" | |
362 | ||
363 | ------------ | |
364 | ||
365 | Various commands read from the configuration file and adjust | |
366 | their operation accordingly. | |
367 | ||
368 | ||
6c84e2e0 | 369 | Identifier Terminology |
2cf565c5 DG |
370 | ---------------------- |
371 | <object>:: | |
2fa090b6 | 372 | Indicates the object name for any type of object. |
2cf565c5 DG |
373 | |
374 | <blob>:: | |
2fa090b6 | 375 | Indicates a blob object name. |
2cf565c5 DG |
376 | |
377 | <tree>:: | |
2fa090b6 | 378 | Indicates a tree object name. |
2cf565c5 DG |
379 | |
380 | <commit>:: | |
2fa090b6 | 381 | Indicates a commit object name. |
2cf565c5 DG |
382 | |
383 | <tree-ish>:: | |
2fa090b6 | 384 | Indicates a tree, commit or tag object name. A |
6c84e2e0 DG |
385 | command that takes a <tree-ish> argument ultimately wants to |
386 | operate on a <tree> object but automatically dereferences | |
387 | <commit> and <tag> objects that point at a <tree>. | |
2cf565c5 | 388 | |
043d7605 TT |
389 | <commit-ish>:: |
390 | Indicates a commit or tag object name. A | |
391 | command that takes a <commit-ish> argument ultimately wants to | |
392 | operate on a <commit> object but automatically dereferences | |
393 | <tag> objects that point at a <commit>. | |
394 | ||
2cf565c5 DG |
395 | <type>:: |
396 | Indicates that an object type is required. | |
2fa090b6 | 397 | Currently one of: `blob`, `tree`, `commit`, or `tag`. |
2cf565c5 DG |
398 | |
399 | <file>:: | |
2fa090b6 JH |
400 | Indicates a filename - almost always relative to the |
401 | root of the tree structure `GIT_INDEX_FILE` describes. | |
2cf565c5 | 402 | |
c1bdacf9 DG |
403 | Symbolic Identifiers |
404 | -------------------- | |
90933efb | 405 | Any git command accepting any <object> can also use the following |
6c84e2e0 | 406 | symbolic notation: |
c1bdacf9 DG |
407 | |
408 | HEAD:: | |
2fa090b6 JH |
409 | indicates the head of the current branch (i.e. the |
410 | contents of `$GIT_DIR/HEAD`). | |
411 | ||
c1bdacf9 | 412 | <tag>:: |
2fa090b6 JH |
413 | a valid tag 'name' |
414 | (i.e. the contents of `$GIT_DIR/refs/tags/<tag>`). | |
415 | ||
c1bdacf9 | 416 | <head>:: |
2fa090b6 JH |
417 | a valid head 'name' |
418 | (i.e. the contents of `$GIT_DIR/refs/heads/<head>`). | |
419 | ||
d47107d8 | 420 | For a more complete list of ways to spell object names, see |
5162e697 | 421 | "SPECIFYING REVISIONS" section in linkgit:git-rev-parse[1]. |
d47107d8 | 422 | |
c1bdacf9 DG |
423 | |
424 | File/Directory Structure | |
425 | ------------------------ | |
c1bdacf9 | 426 | |
6998e4db | 427 | Please see the linkgit:gitrepository-layout[5] document. |
c1bdacf9 | 428 | |
6998e4db | 429 | Read linkgit:githooks[5] for more details about each hook. |
6250ad1e | 430 | |
c1bdacf9 | 431 | Higher level SCMs may provide and manage additional information in the |
2fa090b6 | 432 | `$GIT_DIR`. |
c1bdacf9 | 433 | |
a1d4aa74 | 434 | |
2cf565c5 DG |
435 | Terminology |
436 | ----------- | |
6998e4db | 437 | Please see linkgit:gitglossary[7]. |
2cf565c5 DG |
438 | |
439 | ||
440 | Environment Variables | |
441 | --------------------- | |
442 | Various git commands use the following environment variables: | |
443 | ||
c1bdacf9 DG |
444 | The git Repository |
445 | ~~~~~~~~~~~~~~~~~~ | |
446 | These environment variables apply to 'all' core git commands. Nb: it | |
447 | is worth noting that they may be used/overridden by SCMS sitting above | |
2fa090b6 | 448 | git so take care if using Cogito etc. |
c1bdacf9 DG |
449 | |
450 | 'GIT_INDEX_FILE':: | |
451 | This environment allows the specification of an alternate | |
5f3aa197 LS |
452 | index file. If not specified, the default of `$GIT_DIR/index` |
453 | is used. | |
c1bdacf9 DG |
454 | |
455 | 'GIT_OBJECT_DIRECTORY':: | |
456 | If the object storage directory is specified via this | |
457 | environment variable then the sha1 directories are created | |
458 | underneath - otherwise the default `$GIT_DIR/objects` | |
459 | directory is used. | |
460 | ||
461 | 'GIT_ALTERNATE_OBJECT_DIRECTORIES':: | |
462 | Due to the immutable nature of git objects, old objects can be | |
463 | archived into shared, read-only directories. This variable | |
80ba074f JS |
464 | specifies a ":" separated (on Windows ";" separated) list |
465 | of git object directories which can be used to search for git | |
466 | objects. New objects will not be written to these directories. | |
c1bdacf9 DG |
467 | |
468 | 'GIT_DIR':: | |
2fa090b6 JH |
469 | If the 'GIT_DIR' environment variable is set then it |
470 | specifies a path to use instead of the default `.git` | |
471 | for the base of the repository. | |
c1bdacf9 | 472 | |
892c41b9 ML |
473 | 'GIT_WORK_TREE':: |
474 | Set the path to the working tree. The value will not be | |
475 | used in combination with repositories found automatically in | |
476 | a .git directory (i.e. $GIT_DIR is not set). | |
477 | This can also be controlled by the '--work-tree' command line | |
478 | option and the core.worktree configuration variable. | |
479 | ||
0454dd93 DR |
480 | 'GIT_CEILING_DIRECTORIES':: |
481 | This should be a colon-separated list of absolute paths. | |
482 | If set, it is a list of directories that git should not chdir | |
483 | up into while looking for a repository directory. | |
484 | It will not exclude the current working directory or | |
485 | a GIT_DIR set on the command line or in the environment. | |
486 | (Useful for excluding slow-loading network directories.) | |
487 | ||
c1bdacf9 DG |
488 | git Commits |
489 | ~~~~~~~~~~~ | |
490 | 'GIT_AUTHOR_NAME':: | |
491 | 'GIT_AUTHOR_EMAIL':: | |
492 | 'GIT_AUTHOR_DATE':: | |
493 | 'GIT_COMMITTER_NAME':: | |
494 | 'GIT_COMMITTER_EMAIL':: | |
4e58bf97 | 495 | 'GIT_COMMITTER_DATE':: |
28a94f88 | 496 | 'EMAIL':: |
5162e697 | 497 | see linkgit:git-commit-tree[1] |
c1bdacf9 DG |
498 | |
499 | git Diffs | |
500 | ~~~~~~~~~ | |
d81ed1b5 | 501 | 'GIT_DIFF_OPTS':: |
fde97d8a SE |
502 | Only valid setting is "--unified=??" or "-u??" to set the |
503 | number of context lines shown when a unified diff is created. | |
504 | This takes precedence over any "-U" or "--unified" option | |
505 | value passed on the git diff command line. | |
506 | ||
d81ed1b5 | 507 | 'GIT_EXTERNAL_DIFF':: |
fde97d8a SE |
508 | When the environment variable 'GIT_EXTERNAL_DIFF' is set, the |
509 | program named by it is called, instead of the diff invocation | |
510 | described above. For a path that is added, removed, or modified, | |
511 | 'GIT_EXTERNAL_DIFF' is called with 7 parameters: | |
512 | ||
513 | path old-file old-hex old-mode new-file new-hex new-mode | |
514 | + | |
515 | where: | |
516 | ||
517 | <old|new>-file:: are files GIT_EXTERNAL_DIFF can use to read the | |
518 | contents of <old|new>, | |
519 | <old|new>-hex:: are the 40-hexdigit SHA1 hashes, | |
520 | <old|new>-mode:: are the octal representation of the file modes. | |
521 | ||
522 | + | |
523 | The file parameters can point at the user's working file | |
524 | (e.g. `new-file` in "git-diff-files"), `/dev/null` (e.g. `old-file` | |
525 | when a new file is added), or a temporary file (e.g. `old-file` in the | |
526 | index). 'GIT_EXTERNAL_DIFF' should not worry about unlinking the | |
527 | temporary file --- it is removed when 'GIT_EXTERNAL_DIFF' exits. | |
528 | + | |
529 | For a path that is unmerged, 'GIT_EXTERNAL_DIFF' is called with 1 | |
530 | parameter, <path>. | |
2cf565c5 | 531 | |
575ba9d6 ML |
532 | other |
533 | ~~~~~ | |
dbddb714 JN |
534 | 'GIT_MERGE_VERBOSITY':: |
535 | A number controlling the amount of output shown by | |
536 | the recursive merge strategy. Overrides merge.verbosity. | |
5162e697 | 537 | See linkgit:git-merge[1] |
dbddb714 | 538 | |
c27d205a | 539 | 'GIT_PAGER':: |
a7738c77 SG |
540 | This environment variable overrides `$PAGER`. If it is set |
541 | to an empty string or to the value "cat", git will not launch | |
ab54cd6c JN |
542 | a pager. See also the `core.pager` option in |
543 | linkgit:git-config[1]. | |
c27d205a | 544 | |
d5538b41 | 545 | 'GIT_SSH':: |
ba020ef5 JN |
546 | If this environment variable is set then 'git-fetch' |
547 | and 'git-push' will use this command instead | |
2fd02c92 | 548 | of 'ssh' when they need to connect to a remote system. |
483bc4f0 | 549 | The '$GIT_SSH' command will be given exactly two arguments: |
d5538b41 SP |
550 | the 'username@host' (or just 'host') from the URL and the |
551 | shell command to execute on that remote system. | |
552 | + | |
553 | To pass options to the program that you want to list in GIT_SSH | |
554 | you will need to wrap the program and options into a shell script, | |
555 | then set GIT_SSH to refer to the shell script. | |
556 | + | |
557 | Usually it is easier to configure any desired options through your | |
558 | personal `.ssh/config` file. Please consult your ssh documentation | |
559 | for further details. | |
560 | ||
06f59e9f TT |
561 | 'GIT_FLUSH':: |
562 | If this environment variable is set to "1", then commands such | |
ba020ef5 JN |
563 | as 'git-blame' (in incremental mode), 'git-rev-list', 'git-log', |
564 | and 'git-whatchanged' will force a flush of the output stream | |
06f59e9f TT |
565 | after each commit-oriented record have been flushed. If this |
566 | variable is set to "0", the output of these commands will be done | |
567 | using completely buffered I/O. If this environment variable is | |
568 | not set, git will choose buffered or record-oriented flushing | |
569 | based on whether stdout appears to be redirected to a file or not. | |
570 | ||
575ba9d6 | 571 | 'GIT_TRACE':: |
2886bdb1 CC |
572 | If this variable is set to "1", "2" or "true" (comparison |
573 | is case insensitive), git will print `trace:` messages on | |
575ba9d6 ML |
574 | stderr telling about alias expansion, built-in command |
575 | execution and external command execution. | |
2886bdb1 CC |
576 | If this variable is set to an integer value greater than 1 |
577 | and lower than 10 (strictly) then git will interpret this | |
578 | value as an open file descriptor and will try to write the | |
579 | trace messages into this file descriptor. | |
580 | Alternatively, if this variable is set to an absolute path | |
581 | (starting with a '/' character), git will interpret this | |
582 | as a file path and will try to write the trace messages | |
583 | into it. | |
575ba9d6 | 584 | |
8db9307c JH |
585 | Discussion[[Discussion]] |
586 | ------------------------ | |
40dac517 BF |
587 | |
588 | More detail on the following is available from the | |
589 | link:user-manual.html#git-concepts[git concepts chapter of the | |
6998e4db | 590 | user-manual] and linkgit:gitcore-tutorial[7]. |
40dac517 BF |
591 | |
592 | A git project normally consists of a working directory with a ".git" | |
593 | subdirectory at the top level. The .git directory contains, among other | |
594 | things, a compressed object database representing the complete history | |
595 | of the project, an "index" file which links that history to the current | |
596 | contents of the working tree, and named pointers into that history such | |
597 | as tags and branch heads. | |
598 | ||
599 | The object database contains objects of three main types: blobs, which | |
600 | hold file data; trees, which point to blobs and other trees to build up | |
02ff6250 | 601 | directory hierarchies; and commits, which each reference a single tree |
40dac517 BF |
602 | and some number of parent commits. |
603 | ||
604 | The commit, equivalent to what other systems call a "changeset" or | |
605 | "version", represents a step in the project's history, and each parent | |
606 | represents an immediately preceding step. Commits with more than one | |
607 | parent represent merges of independent lines of development. | |
608 | ||
609 | All objects are named by the SHA1 hash of their contents, normally | |
610 | written as a string of 40 hex digits. Such names are globally unique. | |
611 | The entire history leading up to a commit can be vouched for by signing | |
612 | just that commit. A fourth object type, the tag, is provided for this | |
613 | purpose. | |
614 | ||
615 | When first created, objects are stored in individual files, but for | |
616 | efficiency may later be compressed together into "pack files". | |
617 | ||
618 | Named pointers called refs mark interesting points in history. A ref | |
619 | may contain the SHA1 name of an object or the name of another ref. Refs | |
620 | with names beginning `ref/head/` contain the SHA1 name of the most | |
02ff6250 | 621 | recent commit (or "head") of a branch under development. SHA1 names of |
40dac517 BF |
622 | tags of interest are stored under `ref/tags/`. A special ref named |
623 | `HEAD` contains the name of the currently checked-out branch. | |
624 | ||
625 | The index file is initialized with a list of all paths and, for each | |
626 | path, a blob object and a set of attributes. The blob object represents | |
627 | the contents of the file as of the head of the current branch. The | |
628 | attributes (last modified time, size, etc.) are taken from the | |
629 | corresponding file in the working tree. Subsequent changes to the | |
630 | working tree can be found by comparing these attributes. The index may | |
631 | be updated with new content, and new commits may be created from the | |
632 | content stored in the index. | |
633 | ||
634 | The index is also capable of storing multiple entries (called "stages") | |
635 | for a given pathname. These stages are used to hold the various | |
636 | unmerged version of a file when a merge is in progress. | |
6c84e2e0 | 637 | |
cb22bc44 AE |
638 | Authors |
639 | ------- | |
9755afbd | 640 | * git's founding father is Linus Torvalds <torvalds@osdl.org>. |
947ad2e1 | 641 | * The current git nurse is Junio C Hamano <gitster@pobox.com>. |
0240e21a | 642 | * The git potty was written by Andreas Ericsson <ae@op5.se>. |
9755afbd | 643 | * General upbringing is handled by the git-list <git@vger.kernel.org>. |
2cf565c5 DG |
644 | |
645 | Documentation | |
646 | -------------- | |
9755afbd JH |
647 | The documentation for git suite was started by David Greaves |
648 | <david@dgreaves.com>, and later enhanced greatly by the | |
649 | contributors on the git-list <git@vger.kernel.org>. | |
2cf565c5 | 650 | |
497c8331 CC |
651 | SEE ALSO |
652 | -------- | |
653 | linkgit:gittutorial[7], linkgit:gittutorial-2[7], | |
5cbef01a | 654 | link:everyday.html[Everyday Git], linkgit:gitcvs-migration[7], |
497c8331 | 655 | linkgit:gitglossary[7], linkgit:gitcore-tutorial[7], |
801a011d TR |
656 | linkgit:gitcli[7], link:user-manual.html[The Git User's Manual], |
657 | linkgit:gitworkflows[7] | |
497c8331 | 658 | |
2cf565c5 DG |
659 | GIT |
660 | --- | |
9e1f0a85 | 661 | Part of the linkgit:git[1] suite |