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