]>
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] |
44e1e4d6 | 12 | 'git' [--version] [--help] [-C <path>] [-c <name>=<value>] |
68e4b552 | 13 | [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path] |
7213c288 | 14 | [-p|--paginate|-P|--no-pager] [--no-replace-objects] [--bare] |
d49483f0 | 15 | [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>] |
74866d75 | 16 | [--super-prefix=<path>] |
68e4b552 | 17 | <command> [<args>] |
2cf565c5 DG |
18 | |
19 | DESCRIPTION | |
20 | ----------- | |
23091e95 BF |
21 | Git is a fast, scalable, distributed revision control system with an |
22 | unusually rich command set that provides both high-level operations | |
23 | and full access to internals. | |
24 | ||
6998e4db | 25 | See linkgit:gittutorial[7] to get started, then see |
673151a9 | 26 | linkgit:giteveryday[7] for a useful minimum set of |
7687ae98 JH |
27 | commands. The link:user-manual.html[Git User's Manual] has a more |
28 | in-depth introduction. | |
cb22bc44 | 29 | |
7687ae98 | 30 | After you mastered the basic concepts, you can come back to this |
2de9b711 TA |
31 | page to learn what commands Git offers. You can learn more about |
32 | individual Git commands with "git help command". linkgit:gitcli[7] | |
06ab60c0 | 33 | manual page gives you an overview of the command-line command syntax. |
4514ad4f | 34 | |
f7935827 JN |
35 | A formatted and hyperlinked copy of the latest Git documentation |
36 | can be viewed at `https://git.github.io/htmldocs/git.html`. | |
34b604af | 37 | |
26cfcfbf | 38 | |
cb22bc44 AE |
39 | OPTIONS |
40 | ------- | |
41 | --version:: | |
2de9b711 | 42 | Prints the Git suite version that the 'git' program came from. |
cb22bc44 AE |
43 | |
44 | --help:: | |
a87cd02c | 45 | Prints the synopsis and a list of the most commonly used |
bcf9626a | 46 | commands. If the option `--all` or `-a` is given then all |
2de9b711 | 47 | available commands are printed. If a Git command is named this |
0f6f195b | 48 | option will bring up the manual page for that command. |
45533d26 CC |
49 | + |
50 | Other options are available to control how the manual page is | |
5162e697 | 51 | displayed. See linkgit:git-help[1] for more information, |
db5d6666 JN |
52 | because `git --help ...` is converted internally into `git |
53 | help ...`. | |
cb22bc44 | 54 | |
44e1e4d6 NR |
55 | -C <path>:: |
56 | Run as if git was started in '<path>' instead of the current working | |
57 | directory. When multiple `-C` options are given, each subsequent | |
58 | non-absolute `-C <path>` is interpreted relative to the preceding `-C | |
1a64e07d SG |
59 | <path>`. If '<path>' is present but empty, e.g. `-C ""`, then the |
60 | current working directory is left unchanged. | |
44e1e4d6 NR |
61 | + |
62 | This option affects options that expect path name like `--git-dir` and | |
63 | `--work-tree` in that their interpretations of the path names would be | |
64 | made relative to the working directory caused by the `-C` option. For | |
65 | example the following invocations are equivalent: | |
66 | ||
67 | git --git-dir=a.git --work-tree=b -C c status | |
68 | git --git-dir=c/a.git --work-tree=c/b status | |
69 | ||
8b1fa778 AR |
70 | -c <name>=<value>:: |
71 | Pass a configuration parameter to the command. The value | |
72 | given will override values from configuration files. | |
73 | The <name> is expected in the same format as listed by | |
74 | 'git config' (subkeys separated by dots). | |
a789ca70 JH |
75 | + |
76 | Note that omitting the `=` in `git -c foo.bar ...` is allowed and sets | |
77 | `foo.bar` to the boolean true value (just like `[foo]bar` would in a | |
78 | config file). Including the equals but with an empty value (like `git -c | |
5e633326 | 79 | foo.bar= ...`) sets `foo.bar` to the empty string which `git config |
ed3bb3df | 80 | --type=bool` will convert to `false`. |
8b1fa778 | 81 | |
62b4698e | 82 | --exec-path[=<path>]:: |
2de9b711 | 83 | Path to wherever your core Git programs are installed. |
cb22bc44 | 84 | This can also be controlled by setting the GIT_EXEC_PATH |
56992f76 | 85 | environment variable. If no path is given, 'git' will print |
cb22bc44 AE |
86 | the current setting and then exit. |
87 | ||
89a56bfb | 88 | --html-path:: |
2de9b711 | 89 | Print the path, without trailing slash, where Git's HTML |
239b5ed9 | 90 | documentation is installed and exit. |
89a56bfb | 91 | |
f2dd8c37 | 92 | --man-path:: |
239b5ed9 | 93 | Print the manpath (see `man(1)`) for the man pages for |
2de9b711 | 94 | this version of Git and exit. |
f2dd8c37 JS |
95 | |
96 | --info-path:: | |
239b5ed9 | 97 | Print the path where the Info files documenting this |
2de9b711 | 98 | version of Git are installed and exit. |
89a56bfb | 99 | |
3240240f SB |
100 | -p:: |
101 | --paginate:: | |
06300d97 JN |
102 | Pipe all output into 'less' (or if set, $PAGER) if standard |
103 | output is a terminal. This overrides the `pager.<cmd>` | |
104 | configuration options (see the "Configuration Mechanism" section | |
105 | below). | |
6acbcb92 | 106 | |
7213c288 | 107 | -P:: |
463a849d | 108 | --no-pager:: |
2de9b711 | 109 | Do not pipe Git output into a pager. |
463a849d | 110 | |
6acbcb92 JS |
111 | --git-dir=<path>:: |
112 | Set the path to the repository. This can also be controlled by | |
47d81b5c | 113 | setting the `GIT_DIR` environment variable. It can be an absolute |
302cc11a | 114 | path or relative path to current working directory. |
6acbcb92 | 115 | |
892c41b9 | 116 | --work-tree=<path>:: |
ea472c1e JH |
117 | Set the path to the working tree. It can be an absolute path |
118 | or a path relative to the current working directory. | |
892c41b9 ML |
119 | This can also be controlled by setting the GIT_WORK_TREE |
120 | environment variable and the core.worktree configuration | |
ea472c1e JH |
121 | variable (see core.worktree in linkgit:git-config[1] for a |
122 | more detailed discussion). | |
892c41b9 | 123 | |
d49483f0 | 124 | --namespace=<path>:: |
2de9b711 | 125 | Set the Git namespace. See linkgit:gitnamespaces[7] for more |
d49483f0 JT |
126 | details. Equivalent to setting the `GIT_NAMESPACE` environment |
127 | variable. | |
128 | ||
74866d75 BW |
129 | --super-prefix=<path>:: |
130 | Currently for internal use only. Set a prefix which gives a path from | |
131 | above a repository down to its root. One use is to give submodules | |
132 | context about the superproject that invoked it. | |
133 | ||
6acbcb92 | 134 | --bare:: |
9277d602 JH |
135 | Treat the repository as a bare repository. If GIT_DIR |
136 | environment is not set, it is set to the current working | |
137 | directory. | |
138 | ||
b0fa7ab5 | 139 | --no-replace-objects:: |
2de9b711 | 140 | Do not use replacement refs to replace Git objects. See |
b0fa7ab5 CC |
141 | linkgit:git-replace[1] for more information. |
142 | ||
823ab40f | 143 | --literal-pathspecs:: |
a16bf9dd NTND |
144 | Treat pathspecs literally (i.e. no globbing, no pathspec magic). |
145 | This is equivalent to setting the `GIT_LITERAL_PATHSPECS` environment | |
823ab40f JK |
146 | variable to `1`. |
147 | ||
6fb02165 | 148 | --glob-pathspecs:: |
bd30c2e4 NTND |
149 | Add "glob" magic to all pathspec. This is equivalent to setting |
150 | the `GIT_GLOB_PATHSPECS` environment variable to `1`. Disabling | |
151 | globbing on individual pathspecs can be done using pathspec | |
152 | magic ":(literal)" | |
153 | ||
6fb02165 | 154 | --noglob-pathspecs:: |
bd30c2e4 NTND |
155 | Add "literal" magic to all pathspec. This is equivalent to setting |
156 | the `GIT_NOGLOB_PATHSPECS` environment variable to `1`. Enabling | |
157 | globbing on individual pathspecs can be done using pathspec | |
158 | magic ":(glob)" | |
9755afbd | 159 | |
6fb02165 | 160 | --icase-pathspecs:: |
93d93537 NTND |
161 | Add "icase" magic to all pathspec. This is equivalent to setting |
162 | the `GIT_ICASE_PATHSPECS` environment variable to `1`. | |
9755afbd | 163 | |
27344d6a JK |
164 | --no-optional-locks:: |
165 | Do not perform optional operations that require locks. This is | |
166 | equivalent to setting the `GIT_OPTIONAL_LOCKS` to `0`. | |
167 | ||
0089521c NTND |
168 | --list-cmds=group[,group...]:: |
169 | List commands by group. This is an internal/experimental | |
170 | option and may change or be removed in the future. Supported | |
171 | groups are: builtins, parseopt (builtin commands that use | |
6bb2dc0b | 172 | parse-options), main (all commands in libexec directory), |
3c777767 | 173 | others (all other commands in `$PATH` that have git- prefix), |
e11dca10 | 174 | list-<category> (see categories in command-list.txt), |
6532f374 NTND |
175 | nohelpers (exclude helper commands), alias and config |
176 | (retrieve command list from config variable completion.commands) | |
0089521c | 177 | |
23091e95 BF |
178 | GIT COMMANDS |
179 | ------------ | |
9755afbd | 180 | |
2de9b711 | 181 | We divide Git into high level ("porcelain") commands and low level |
23091e95 | 182 | ("plumbing") commands. |
8b15e2fb | 183 | |
23091e95 BF |
184 | High-level commands (porcelain) |
185 | ------------------------------- | |
186 | ||
187 | We separate the porcelain commands into the main commands and some | |
188 | ancillary user utilities. | |
189 | ||
190 | Main porcelain commands | |
191 | ~~~~~~~~~~~~~~~~~~~~~~~ | |
905197de | 192 | |
377e8139 | 193 | include::cmds-mainporcelain.txt[] |
e31bb3bb | 194 | |
90933efb | 195 | Ancillary Commands |
23091e95 | 196 | ~~~~~~~~~~~~~~~~~~ |
2f2de9b4 JH |
197 | Manipulators: |
198 | ||
377e8139 | 199 | include::cmds-ancillarymanipulators.txt[] |
204ee6a9 | 200 | |
90933efb | 201 | Interrogators: |
204ee6a9 | 202 | |
377e8139 | 203 | include::cmds-ancillaryinterrogators.txt[] |
7fc9d69f | 204 | |
89bf2077 JH |
205 | |
206 | Interacting with Others | |
207 | ~~~~~~~~~~~~~~~~~~~~~~~ | |
208 | ||
209 | These commands are to interact with foreign SCM and with other | |
210 | people via patch over e-mail. | |
211 | ||
212 | include::cmds-foreignscminterface.txt[] | |
213 | ||
214 | ||
b1f33d62 RR |
215 | Low-level commands (plumbing) |
216 | ----------------------------- | |
217 | ||
2de9b711 | 218 | Although Git includes its |
b1f33d62 RR |
219 | own porcelain layer, its low-level commands are sufficient to support |
220 | development of alternative porcelains. Developers of such porcelains | |
5162e697 DM |
221 | might start by reading about linkgit:git-update-index[1] and |
222 | linkgit:git-read-tree[1]. | |
b1f33d62 | 223 | |
89bf2077 JH |
224 | The interface (input, output, set of options and the semantics) |
225 | to these low-level commands are meant to be a lot more stable | |
226 | than Porcelain level commands, because these commands are | |
227 | primarily for scripted use. The interface to Porcelain commands | |
228 | on the other hand are subject to change in order to improve the | |
229 | end user experience. | |
230 | ||
231 | The following description divides | |
232 | the low-level commands into commands that manipulate objects (in | |
b1f33d62 RR |
233 | the repository, index, and working tree), commands that interrogate and |
234 | compare objects, and commands that move objects and references between | |
235 | repositories. | |
236 | ||
89bf2077 | 237 | |
b1f33d62 RR |
238 | Manipulation commands |
239 | ~~~~~~~~~~~~~~~~~~~~~ | |
b1f33d62 | 240 | |
377e8139 | 241 | include::cmds-plumbingmanipulators.txt[] |
b1f33d62 RR |
242 | |
243 | ||
244 | Interrogation commands | |
245 | ~~~~~~~~~~~~~~~~~~~~~~ | |
246 | ||
377e8139 | 247 | include::cmds-plumbinginterrogators.txt[] |
b1f33d62 RR |
248 | |
249 | In general, the interrogate commands do not touch the files in | |
250 | the working tree. | |
251 | ||
252 | ||
253 | Synching repositories | |
254 | ~~~~~~~~~~~~~~~~~~~~~ | |
255 | ||
377e8139 | 256 | include::cmds-synchingrepositories.txt[] |
b1f33d62 | 257 | |
57f6ec02 | 258 | The following are helper commands used by the above; end users |
89bf2077 JH |
259 | typically do not use them directly. |
260 | ||
261 | include::cmds-synchelpers.txt[] | |
262 | ||
263 | ||
264 | Internal helper commands | |
265 | ~~~~~~~~~~~~~~~~~~~~~~~~ | |
266 | ||
267 | These are internal helper commands used by other commands; end | |
268 | users typically do not use them directly. | |
269 | ||
270 | include::cmds-purehelpers.txt[] | |
271 | ||
b1f33d62 | 272 | |
5773c9f2 JH |
273 | Configuration Mechanism |
274 | ----------------------- | |
275 | ||
c0179c0d MM |
276 | Git uses a simple text format to store customizations that are per |
277 | repository and are per user. Such a configuration file may look | |
278 | like this: | |
5773c9f2 JH |
279 | |
280 | ------------ | |
281 | # | |
2fa090b6 | 282 | # A '#' or ';' character indicates a comment. |
5773c9f2 JH |
283 | # |
284 | ||
285 | ; core variables | |
286 | [core] | |
287 | ; Don't trust file modes | |
288 | filemode = false | |
289 | ||
290 | ; user identity | |
291 | [user] | |
292 | name = "Junio C Hamano" | |
c0179c0d | 293 | email = "gitster@pobox.com" |
5773c9f2 JH |
294 | |
295 | ------------ | |
296 | ||
297 | Various commands read from the configuration file and adjust | |
06300d97 | 298 | their operation accordingly. See linkgit:git-config[1] for a |
c0179c0d | 299 | list and more details about the configuration mechanism. |
5773c9f2 JH |
300 | |
301 | ||
6c84e2e0 | 302 | Identifier Terminology |
2cf565c5 DG |
303 | ---------------------- |
304 | <object>:: | |
2fa090b6 | 305 | Indicates the object name for any type of object. |
2cf565c5 DG |
306 | |
307 | <blob>:: | |
2fa090b6 | 308 | Indicates a blob object name. |
2cf565c5 DG |
309 | |
310 | <tree>:: | |
2fa090b6 | 311 | Indicates a tree object name. |
2cf565c5 DG |
312 | |
313 | <commit>:: | |
2fa090b6 | 314 | Indicates a commit object name. |
2cf565c5 DG |
315 | |
316 | <tree-ish>:: | |
2fa090b6 | 317 | Indicates a tree, commit or tag object name. A |
6c84e2e0 DG |
318 | command that takes a <tree-ish> argument ultimately wants to |
319 | operate on a <tree> object but automatically dereferences | |
320 | <commit> and <tag> objects that point at a <tree>. | |
2cf565c5 | 321 | |
043d7605 TT |
322 | <commit-ish>:: |
323 | Indicates a commit or tag object name. A | |
324 | command that takes a <commit-ish> argument ultimately wants to | |
325 | operate on a <commit> object but automatically dereferences | |
326 | <tag> objects that point at a <commit>. | |
327 | ||
2cf565c5 DG |
328 | <type>:: |
329 | Indicates that an object type is required. | |
2fa090b6 | 330 | Currently one of: `blob`, `tree`, `commit`, or `tag`. |
2cf565c5 DG |
331 | |
332 | <file>:: | |
2fa090b6 JH |
333 | Indicates a filename - almost always relative to the |
334 | root of the tree structure `GIT_INDEX_FILE` describes. | |
2cf565c5 | 335 | |
c1bdacf9 DG |
336 | Symbolic Identifiers |
337 | -------------------- | |
2de9b711 | 338 | Any Git command accepting any <object> can also use the following |
6c84e2e0 | 339 | symbolic notation: |
c1bdacf9 DG |
340 | |
341 | HEAD:: | |
0abcfbff | 342 | indicates the head of the current branch. |
2fa090b6 | 343 | |
c1bdacf9 | 344 | <tag>:: |
2fa090b6 | 345 | a valid tag 'name' |
0abcfbff | 346 | (i.e. a `refs/tags/<tag>` reference). |
2fa090b6 | 347 | |
c1bdacf9 | 348 | <head>:: |
2fa090b6 | 349 | a valid head 'name' |
0abcfbff | 350 | (i.e. a `refs/heads/<head>` reference). |
2fa090b6 | 351 | |
d47107d8 | 352 | For a more complete list of ways to spell object names, see |
9d83e382 | 353 | "SPECIFYING REVISIONS" section in linkgit:gitrevisions[7]. |
d47107d8 | 354 | |
c1bdacf9 DG |
355 | |
356 | File/Directory Structure | |
357 | ------------------------ | |
c1bdacf9 | 358 | |
6998e4db | 359 | Please see the linkgit:gitrepository-layout[5] document. |
c1bdacf9 | 360 | |
6998e4db | 361 | Read linkgit:githooks[5] for more details about each hook. |
6250ad1e | 362 | |
c1bdacf9 | 363 | Higher level SCMs may provide and manage additional information in the |
2fa090b6 | 364 | `$GIT_DIR`. |
c1bdacf9 | 365 | |
a1d4aa74 | 366 | |
2cf565c5 DG |
367 | Terminology |
368 | ----------- | |
6998e4db | 369 | Please see linkgit:gitglossary[7]. |
2cf565c5 DG |
370 | |
371 | ||
372 | Environment Variables | |
373 | --------------------- | |
2de9b711 | 374 | Various Git commands use the following environment variables: |
2cf565c5 | 375 | |
2de9b711 | 376 | The Git Repository |
c1bdacf9 | 377 | ~~~~~~~~~~~~~~~~~~ |
2de9b711 | 378 | These environment variables apply to 'all' core Git commands. Nb: it |
c1bdacf9 | 379 | is worth noting that they may be used/overridden by SCMS sitting above |
f25b98e6 | 380 | Git so take care if using a foreign front-end. |
c1bdacf9 | 381 | |
eee7f4a2 | 382 | `GIT_INDEX_FILE`:: |
c1bdacf9 | 383 | This environment allows the specification of an alternate |
5f3aa197 LS |
384 | index file. If not specified, the default of `$GIT_DIR/index` |
385 | is used. | |
c1bdacf9 | 386 | |
eee7f4a2 | 387 | `GIT_INDEX_VERSION`:: |
136347d7 TG |
388 | This environment variable allows the specification of an index |
389 | version for new repositories. It won't affect existing index | |
70320541 NTND |
390 | files. By default index file version 2 or 3 is used. See |
391 | linkgit:git-update-index[1] for more information. | |
136347d7 | 392 | |
eee7f4a2 | 393 | `GIT_OBJECT_DIRECTORY`:: |
c1bdacf9 DG |
394 | If the object storage directory is specified via this |
395 | environment variable then the sha1 directories are created | |
396 | underneath - otherwise the default `$GIT_DIR/objects` | |
397 | directory is used. | |
398 | ||
eee7f4a2 | 399 | `GIT_ALTERNATE_OBJECT_DIRECTORIES`:: |
2de9b711 | 400 | Due to the immutable nature of Git objects, old objects can be |
c1bdacf9 | 401 | archived into shared, read-only directories. This variable |
80ba074f | 402 | specifies a ":" separated (on Windows ";" separated) list |
2de9b711 | 403 | of Git object directories which can be used to search for Git |
80ba074f | 404 | objects. New objects will not be written to these directories. |
cf3c6352 | 405 | + |
ad471949 AH |
406 | Entries that begin with `"` (double-quote) will be interpreted |
407 | as C-style quoted paths, removing leading and trailing | |
408 | double-quotes and respecting backslash escapes. E.g., the value | |
409 | `"path-with-\"-and-:-in-it":vanilla-path` has two paths: | |
410 | `path-with-"-and-:-in-it` and `vanilla-path`. | |
c1bdacf9 | 411 | |
eee7f4a2 TR |
412 | `GIT_DIR`:: |
413 | If the `GIT_DIR` environment variable is set then it | |
2fa090b6 JH |
414 | specifies a path to use instead of the default `.git` |
415 | for the base of the repository. | |
bcf9626a | 416 | The `--git-dir` command-line option also sets this value. |
c1bdacf9 | 417 | |
eee7f4a2 | 418 | `GIT_WORK_TREE`:: |
a758a349 | 419 | Set the path to the root of the working tree. |
bcf9626a | 420 | This can also be controlled by the `--work-tree` command-line |
892c41b9 ML |
421 | option and the core.worktree configuration variable. |
422 | ||
eee7f4a2 | 423 | `GIT_NAMESPACE`:: |
2de9b711 | 424 | Set the Git namespace; see linkgit:gitnamespaces[7] for details. |
bcf9626a | 425 | The `--namespace` command-line option also sets this value. |
d49483f0 | 426 | |
eee7f4a2 | 427 | `GIT_CEILING_DIRECTORIES`:: |
7ec30aaa | 428 | This should be a colon-separated list of absolute paths. If |
3e07d268 | 429 | set, it is a list of directories that Git should not chdir up |
7ec30aaa MH |
430 | into while looking for a repository directory (useful for |
431 | excluding slow-loading network directories). It will not | |
432 | exclude the current working directory or a GIT_DIR set on the | |
433 | command line or in the environment. Normally, Git has to read | |
434 | the entries in this list and resolve any symlink that | |
435 | might be present in order to compare them with the current | |
436 | directory. However, if even this access is slow, you | |
437 | can add an empty entry to the list to tell Git that the | |
438 | subsequent entries are not symlinks and needn't be resolved; | |
439 | e.g., | |
eee7f4a2 | 440 | `GIT_CEILING_DIRECTORIES=/maybe/symlink::/very/slow/non/symlink`. |
0454dd93 | 441 | |
eee7f4a2 | 442 | `GIT_DISCOVERY_ACROSS_FILESYSTEM`:: |
e6405517 | 443 | When run in a directory that does not have ".git" repository |
2de9b711 | 444 | directory, Git tries to find such a directory in the parent |
e6405517 JH |
445 | directories to find the top of the working tree, but by default it |
446 | does not cross filesystem boundaries. This environment variable | |
2de9b711 | 447 | can be set to true to tell Git not to stop at filesystem |
eee7f4a2 TR |
448 | boundaries. Like `GIT_CEILING_DIRECTORIES`, this will not affect |
449 | an explicit repository directory set via `GIT_DIR` or on the | |
cf87463e | 450 | command line. |
8030e442 | 451 | |
eee7f4a2 | 452 | `GIT_COMMON_DIR`:: |
c7b3a3d2 NTND |
453 | If this variable is set to a path, non-worktree files that are |
454 | normally in $GIT_DIR will be taken from this path | |
455 | instead. Worktree-specific files such as HEAD or index are | |
529fef20 | 456 | taken from $GIT_DIR. See linkgit:gitrepository-layout[5] and |
1eaca7a5 | 457 | linkgit:git-worktree[1] for |
c7b3a3d2 NTND |
458 | details. This variable has lower precedence than other path |
459 | variables such as GIT_INDEX_FILE, GIT_OBJECT_DIRECTORY... | |
460 | ||
2de9b711 | 461 | Git Commits |
c1bdacf9 | 462 | ~~~~~~~~~~~ |
eee7f4a2 TR |
463 | `GIT_AUTHOR_NAME`:: |
464 | `GIT_AUTHOR_EMAIL`:: | |
465 | `GIT_AUTHOR_DATE`:: | |
466 | `GIT_COMMITTER_NAME`:: | |
467 | `GIT_COMMITTER_EMAIL`:: | |
468 | `GIT_COMMITTER_DATE`:: | |
28a94f88 | 469 | 'EMAIL':: |
5162e697 | 470 | see linkgit:git-commit-tree[1] |
c1bdacf9 | 471 | |
2de9b711 | 472 | Git Diffs |
c1bdacf9 | 473 | ~~~~~~~~~ |
eee7f4a2 | 474 | `GIT_DIFF_OPTS`:: |
fde97d8a SE |
475 | Only valid setting is "--unified=??" or "-u??" to set the |
476 | number of context lines shown when a unified diff is created. | |
477 | This takes precedence over any "-U" or "--unified" option | |
2de9b711 | 478 | value passed on the Git diff command line. |
fde97d8a | 479 | |
eee7f4a2 TR |
480 | `GIT_EXTERNAL_DIFF`:: |
481 | When the environment variable `GIT_EXTERNAL_DIFF` is set, the | |
fde97d8a SE |
482 | program named by it is called, instead of the diff invocation |
483 | described above. For a path that is added, removed, or modified, | |
eee7f4a2 | 484 | `GIT_EXTERNAL_DIFF` is called with 7 parameters: |
fde97d8a SE |
485 | |
486 | path old-file old-hex old-mode new-file new-hex new-mode | |
487 | + | |
488 | where: | |
489 | ||
490 | <old|new>-file:: are files GIT_EXTERNAL_DIFF can use to read the | |
491 | contents of <old|new>, | |
d5fa1f1a | 492 | <old|new>-hex:: are the 40-hexdigit SHA-1 hashes, |
fde97d8a | 493 | <old|new>-mode:: are the octal representation of the file modes. |
fde97d8a SE |
494 | + |
495 | The file parameters can point at the user's working file | |
496 | (e.g. `new-file` in "git-diff-files"), `/dev/null` (e.g. `old-file` | |
497 | when a new file is added), or a temporary file (e.g. `old-file` in the | |
eee7f4a2 TR |
498 | index). `GIT_EXTERNAL_DIFF` should not worry about unlinking the |
499 | temporary file --- it is removed when `GIT_EXTERNAL_DIFF` exits. | |
fde97d8a | 500 | + |
eee7f4a2 | 501 | For a path that is unmerged, `GIT_EXTERNAL_DIFF` is called with 1 |
fde97d8a | 502 | parameter, <path>. |
ee7fb0b1 | 503 | + |
eee7f4a2 TR |
504 | For each path `GIT_EXTERNAL_DIFF` is called, two environment variables, |
505 | `GIT_DIFF_PATH_COUNTER` and `GIT_DIFF_PATH_TOTAL` are set. | |
ee7fb0b1 | 506 | |
eee7f4a2 | 507 | `GIT_DIFF_PATH_COUNTER`:: |
ee7fb0b1 ZK |
508 | A 1-based counter incremented by one for every path. |
509 | ||
eee7f4a2 | 510 | `GIT_DIFF_PATH_TOTAL`:: |
ee7fb0b1 | 511 | The total number of paths. |
2cf565c5 | 512 | |
575ba9d6 ML |
513 | other |
514 | ~~~~~ | |
eee7f4a2 | 515 | `GIT_MERGE_VERBOSITY`:: |
dbddb714 JN |
516 | A number controlling the amount of output shown by |
517 | the recursive merge strategy. Overrides merge.verbosity. | |
5162e697 | 518 | See linkgit:git-merge[1] |
dbddb714 | 519 | |
eee7f4a2 | 520 | `GIT_PAGER`:: |
a7738c77 | 521 | This environment variable overrides `$PAGER`. If it is set |
2de9b711 | 522 | to an empty string or to the value "cat", Git will not launch |
ab54cd6c JN |
523 | a pager. See also the `core.pager` option in |
524 | linkgit:git-config[1]. | |
c27d205a | 525 | |
eee7f4a2 | 526 | `GIT_EDITOR`:: |
36384c97 | 527 | This environment variable overrides `$EDITOR` and `$VISUAL`. |
2de9b711 | 528 | It is used by several Git commands when, on interactive mode, |
36384c97 RSM |
529 | an editor is to be launched. See also linkgit:git-var[1] |
530 | and the `core.editor` option in linkgit:git-config[1]. | |
531 | ||
eee7f4a2 TR |
532 | `GIT_SSH`:: |
533 | `GIT_SSH_COMMAND`:: | |
39942766 TQ |
534 | If either of these environment variables is set then 'git fetch' |
535 | and 'git push' will use the specified command instead of 'ssh' | |
536 | when they need to connect to a remote system. | |
94b8ae5a BW |
537 | The command-line parameters passed to the configured command are |
538 | determined by the ssh variant. See `ssh.variant` option in | |
539 | linkgit:git-config[1] for details. | |
d5538b41 | 540 | + |
39942766 TQ |
541 | `$GIT_SSH_COMMAND` takes precedence over `$GIT_SSH`, and is interpreted |
542 | by the shell, which allows additional arguments to be included. | |
543 | `$GIT_SSH` on the other hand must be just the path to a program | |
544 | (which can be a wrapper shell script, if additional arguments are | |
545 | needed). | |
d5538b41 SP |
546 | + |
547 | Usually it is easier to configure any desired options through your | |
548 | personal `.ssh/config` file. Please consult your ssh documentation | |
549 | for further details. | |
550 | ||
dd33e077 SF |
551 | `GIT_SSH_VARIANT`:: |
552 | If this environment variable is set, it overrides Git's autodetection | |
553 | whether `GIT_SSH`/`GIT_SSH_COMMAND`/`core.sshCommand` refer to OpenSSH, | |
554 | plink or tortoiseplink. This variable overrides the config setting | |
555 | `ssh.variant` that serves the same purpose. | |
556 | ||
eee7f4a2 | 557 | `GIT_ASKPASS`:: |
2de9b711 | 558 | If this environment variable is set, then Git commands which need to |
453842c9 | 559 | acquire passwords or passphrases (e.g. for HTTP or IMAP authentication) |
06ab60c0 | 560 | will call this program with a suitable prompt as command-line argument |
ae9f6311 | 561 | and read the password from its STDOUT. See also the `core.askPass` |
453842c9 KF |
562 | option in linkgit:git-config[1]. |
563 | ||
eee7f4a2 | 564 | `GIT_TERMINAL_PROMPT`:: |
e652c0eb JK |
565 | If this environment variable is set to `0`, git will not prompt |
566 | on the terminal (e.g., when asking for HTTP authentication). | |
567 | ||
eee7f4a2 | 568 | `GIT_CONFIG_NOSYSTEM`:: |
e8ef401c JN |
569 | Whether to skip reading settings from the system-wide |
570 | `$(prefix)/etc/gitconfig` file. This environment variable can | |
571 | be used along with `$HOME` and `$XDG_CONFIG_HOME` to create a | |
572 | predictable environment for a picky script, or you can set it | |
573 | temporarily to avoid using a buggy `/etc/gitconfig` file while | |
574 | waiting for someone with sufficient permissions to fix it. | |
575 | ||
eee7f4a2 | 576 | `GIT_FLUSH`:: |
06f59e9f | 577 | If this environment variable is set to "1", then commands such |
0b444cdb | 578 | as 'git blame' (in incremental mode), 'git rev-list', 'git log', |
627a8b8d | 579 | 'git check-attr' and 'git check-ignore' will |
f1ed7fea AS |
580 | force a flush of the output stream after each record have been |
581 | flushed. If this | |
06f59e9f TT |
582 | variable is set to "0", the output of these commands will be done |
583 | using completely buffered I/O. If this environment variable is | |
2de9b711 | 584 | not set, Git will choose buffered or record-oriented flushing |
06f59e9f TT |
585 | based on whether stdout appears to be redirected to a file or not. |
586 | ||
eee7f4a2 | 587 | `GIT_TRACE`:: |
eb9250df KB |
588 | Enables general trace messages, e.g. alias expansion, built-in |
589 | command execution and external command execution. | |
590 | + | |
591 | If this variable is set to "1", "2" or "true" (comparison | |
592 | is case insensitive), trace messages will be printed to | |
593 | stderr. | |
594 | + | |
595 | If the variable is set to an integer value greater than 2 | |
596 | and lower than 10 (strictly) then Git will interpret this | |
597 | value as an open file descriptor and will try to write the | |
598 | trace messages into this file descriptor. | |
599 | + | |
600 | Alternatively, if the variable is set to an absolute path | |
601 | (starting with a '/' character), Git will interpret this | |
fa0aeea7 SG |
602 | as a file path and will try to append the trace messages |
603 | to it. | |
eb9250df KB |
604 | + |
605 | Unsetting the variable, or setting it to empty, "0" or | |
606 | "false" (case insensitive) disables trace messages. | |
575ba9d6 | 607 | |
bd76afd1 AV |
608 | `GIT_TRACE_FSMONITOR`:: |
609 | Enables trace messages for the filesystem monitor extension. | |
610 | See `GIT_TRACE` for available trace output options. | |
611 | ||
eee7f4a2 | 612 | `GIT_TRACE_PACK_ACCESS`:: |
67dc598e | 613 | Enables trace messages for all accesses to any packs. For each |
b12ca963 NTND |
614 | access, the pack file name and an offset in the pack is |
615 | recorded. This may be helpful for troubleshooting some | |
616 | pack-related performance problems. | |
eee7f4a2 | 617 | See `GIT_TRACE` for available trace output options. |
b12ca963 | 618 | |
eee7f4a2 | 619 | `GIT_TRACE_PACKET`:: |
eb9250df KB |
620 | Enables trace messages for all packets coming in or out of a |
621 | given program. This can help with debugging object negotiation | |
622 | or other protocol issues. Tracing is turned off at a packet | |
eee7f4a2 TR |
623 | starting with "PACK" (but see `GIT_TRACE_PACKFILE` below). |
624 | See `GIT_TRACE` for available trace output options. | |
eb9250df | 625 | |
eee7f4a2 | 626 | `GIT_TRACE_PACKFILE`:: |
32359838 JK |
627 | Enables tracing of packfiles sent or received by a |
628 | given program. Unlike other trace output, this trace is | |
629 | verbatim: no headers, and no quoting of binary data. You almost | |
630 | certainly want to direct into a file (e.g., | |
631 | `GIT_TRACE_PACKFILE=/tmp/my.pack`) rather than displaying it on | |
632 | the terminal or mixing it with other trace output. | |
633 | + | |
634 | Note that this is currently only implemented for the client side | |
635 | of clones and fetches. | |
636 | ||
eee7f4a2 | 637 | `GIT_TRACE_PERFORMANCE`:: |
578da039 KB |
638 | Enables performance related trace messages, e.g. total execution |
639 | time of each Git command. | |
eee7f4a2 | 640 | See `GIT_TRACE` for available trace output options. |
578da039 | 641 | |
eee7f4a2 | 642 | `GIT_TRACE_SETUP`:: |
eb9250df KB |
643 | Enables trace messages printing the .git, working tree and current |
644 | working directory after Git has completed its setup phase. | |
eee7f4a2 | 645 | See `GIT_TRACE` for available trace output options. |
eb9250df | 646 | |
eee7f4a2 | 647 | `GIT_TRACE_SHALLOW`:: |
eb9250df KB |
648 | Enables trace messages that can help debugging fetching / |
649 | cloning of shallow repositories. | |
eee7f4a2 | 650 | See `GIT_TRACE` for available trace output options. |
1dd278ce | 651 | |
2f84df2c | 652 | `GIT_TRACE_CURL`:: |
74c682d3 EP |
653 | Enables a curl full trace dump of all incoming and outgoing data, |
654 | including descriptive information, of the git transport protocol. | |
2f84df2c JH |
655 | This is similar to doing curl `--trace-ascii` on the command line. |
656 | This option overrides setting the `GIT_CURL_VERBOSE` environment | |
74c682d3 | 657 | variable. |
2f84df2c | 658 | See `GIT_TRACE` for available trace output options. |
74c682d3 | 659 | |
8ba18e6f JT |
660 | `GIT_TRACE_CURL_NO_DATA`:: |
661 | When a curl trace is enabled (see `GIT_TRACE_CURL` above), do not dump | |
662 | data (that is, only dump info lines and headers). | |
663 | ||
e4b75d6a | 664 | `GIT_TRACE2`:: |
04b7e86e | 665 | Enables more detailed trace messages from the "trace2" library. |
e4b75d6a | 666 | Output from `GIT_TRACE2` is a simple text-based format for human |
04b7e86e DS |
667 | readability. |
668 | + | |
4e0d3aa1 SG |
669 | If this variable is set to "1", "2" or "true" (comparison |
670 | is case insensitive), trace messages will be printed to | |
671 | stderr. | |
672 | + | |
673 | If the variable is set to an integer value greater than 2 | |
674 | and lower than 10 (strictly) then Git will interpret this | |
675 | value as an open file descriptor and will try to write the | |
676 | trace messages into this file descriptor. | |
677 | + | |
678 | Alternatively, if the variable is set to an absolute path | |
679 | (starting with a '/' character), Git will interpret this | |
680 | as a file path and will try to append the trace messages | |
681 | to it. If the path already exists and is a directory, the | |
682 | trace messages will be written to files (one per process) | |
683 | in that directory, named according to the last component | |
684 | of the SID and an optional counter (to avoid filename | |
685 | collisions). | |
686 | + | |
687 | In addition, if the variable is set to | |
688 | `af_unix:[<socket_type>:]<absolute-pathname>`, Git will try | |
689 | to open the path as a Unix Domain Socket. The socket type | |
690 | can be either `stream` or `dgram`. | |
691 | + | |
692 | Unsetting the variable, or setting it to empty, "0" or | |
693 | "false" (case insensitive) disables trace messages. | |
694 | + | |
695 | See link:technical/api-trace2.html[Trace2 documentation] | |
696 | for full details. | |
697 | ||
04b7e86e | 698 | |
e4b75d6a | 699 | `GIT_TRACE2_EVENT`:: |
04b7e86e | 700 | This setting writes a JSON-based format that is suited for machine |
4e0d3aa1 SG |
701 | interpretation. |
702 | See `GIT_TRACE2` for available trace output options and | |
703 | link:technical/api-trace2.html[Trace2 documentation] for full details. | |
04b7e86e | 704 | |
e4b75d6a SG |
705 | `GIT_TRACE2_PERF`:: |
706 | In addition to the text-based messages available in `GIT_TRACE2`, this | |
04b7e86e | 707 | setting writes a column-based format for understanding nesting |
4e0d3aa1 SG |
708 | regions. |
709 | See `GIT_TRACE2` for available trace output options and | |
710 | link:technical/api-trace2.html[Trace2 documentation] for full details. | |
04b7e86e | 711 | |
83411783 JT |
712 | `GIT_REDACT_COOKIES`:: |
713 | This can be set to a comma-separated list of strings. When a curl trace | |
714 | is enabled (see `GIT_TRACE_CURL` above), whenever a "Cookies:" header | |
715 | sent by the client is dumped, values of cookies whose key is in that | |
716 | list (case-sensitive) are redacted. | |
717 | ||
eee7f4a2 | 718 | `GIT_LITERAL_PATHSPECS`:: |
2de9b711 | 719 | Setting this variable to `1` will cause Git to treat all |
823ab40f JK |
720 | pathspecs literally, rather than as glob patterns. For example, |
721 | running `GIT_LITERAL_PATHSPECS=1 git log -- '*.c'` will search | |
722 | for commits that touch the path `*.c`, not any paths that the | |
723 | glob `*.c` matches. You might want this if you are feeding | |
2de9b711 | 724 | literal paths to Git (e.g., paths previously given to you by |
823ab40f JK |
725 | `git ls-tree`, `--raw` diff output, etc). |
726 | ||
eee7f4a2 | 727 | `GIT_GLOB_PATHSPECS`:: |
bd30c2e4 NTND |
728 | Setting this variable to `1` will cause Git to treat all |
729 | pathspecs as glob patterns (aka "glob" magic). | |
730 | ||
eee7f4a2 | 731 | `GIT_NOGLOB_PATHSPECS`:: |
bd30c2e4 NTND |
732 | Setting this variable to `1` will cause Git to treat all |
733 | pathspecs as literal (aka "literal" magic). | |
734 | ||
eee7f4a2 | 735 | `GIT_ICASE_PATHSPECS`:: |
93d93537 NTND |
736 | Setting this variable to `1` will cause Git to treat all |
737 | pathspecs as case-insensitive. | |
738 | ||
eee7f4a2 | 739 | `GIT_REFLOG_ACTION`:: |
c3e2d189 JH |
740 | When a ref is updated, reflog entries are created to keep |
741 | track of the reason why the ref was updated (which is | |
742 | typically the name of the high-level command that updated | |
743 | the ref), in addition to the old and new values of the ref. | |
744 | A scripted Porcelain command can use set_reflog_action | |
745 | helper function in `git-sh-setup` to set its name to this | |
746 | variable when it is invoked as the top level command by the | |
747 | end user, to be recorded in the body of the reflog. | |
748 | ||
eee7f4a2 | 749 | `GIT_REF_PARANOIA`:: |
49672f26 JK |
750 | If set to `1`, include broken or badly named refs when iterating |
751 | over lists of refs. In a normal, non-corrupted repository, this | |
752 | does nothing. However, enabling it may help git to detect and | |
753 | abort some operations in the presence of broken refs. Git sets | |
754 | this variable automatically when performing destructive | |
755 | operations like linkgit:git-prune[1]. You should not need to set | |
756 | it yourself unless you want to be paranoid about making sure | |
757 | an operation has touched every ref (e.g., because you are | |
758 | cloning a repository to make a backup). | |
759 | ||
eee7f4a2 | 760 | `GIT_ALLOW_PROTOCOL`:: |
f1762d77 BW |
761 | If set to a colon-separated list of protocols, behave as if |
762 | `protocol.allow` is set to `never`, and each of the listed | |
763 | protocols has `protocol.<name>.allow` set to `always` | |
764 | (overriding any existing configuration). In other words, any | |
765 | protocol not mentioned will be disallowed (i.e., this is a | |
766 | whitelist, not a blacklist). See the description of | |
767 | `protocol.allow` in linkgit:git-config[1] for more details. | |
768 | ||
769 | `GIT_PROTOCOL_FROM_USER`:: | |
770 | Set to 0 to prevent protocols used by fetch/push/clone which are | |
771 | configured to the `user` state. This is useful to restrict recursive | |
772 | submodule initialization from an untrusted repository or for programs | |
773 | which feed potentially-untrusted URLS to git commands. See | |
774 | linkgit:git-config[1] for more details. | |
823ab40f | 775 | |
373d70ef BW |
776 | `GIT_PROTOCOL`:: |
777 | For internal use only. Used in handshaking the wire protocol. | |
778 | Contains a colon ':' separated list of keys with optional values | |
779 | 'key[=value]'. Presence of unknown keys and values must be | |
780 | ignored. | |
781 | ||
27344d6a JK |
782 | `GIT_OPTIONAL_LOCKS`:: |
783 | If set to `0`, Git will complete any requested operation without | |
784 | performing any optional sub-operations that require taking a lock. | |
785 | For example, this will prevent `git status` from refreshing the | |
786 | index as a side effect. This is useful for processes running in | |
787 | the background which do not want to cause lock contention with | |
788 | other operations on the repository. Defaults to `1`. | |
789 | ||
b2f55717 JS |
790 | `GIT_REDIRECT_STDIN`:: |
791 | `GIT_REDIRECT_STDOUT`:: | |
792 | `GIT_REDIRECT_STDERR`:: | |
793 | Windows-only: allow redirecting the standard input/output/error | |
794 | handles to paths specified by the environment variables. This is | |
795 | particularly useful in multi-threaded applications where the | |
796 | canonical way to pass standard handles via `CreateProcess()` is | |
797 | not an option because it would require the handles to be marked | |
798 | inheritable (and consequently *every* spawned process would | |
799 | inherit them, possibly blocking regular Git operations). The | |
800 | primary intended use case is to use named pipes for communication | |
801 | (e.g. `\\.\pipe\my-git-stdin-123`). | |
802 | + | |
803 | Two special values are supported: `off` will simply close the | |
804 | corresponding standard handle, and if `GIT_REDIRECT_STDERR` is | |
805 | `2>&1`, standard error will be redirected to the same handle as | |
806 | standard output. | |
807 | ||
a2cd709d AR |
808 | `GIT_PRINT_SHA1_ELLIPSIS` (deprecated):: |
809 | If set to `yes`, print an ellipsis following an | |
810 | (abbreviated) SHA-1 value. This affects indications of | |
811 | detached HEADs (linkgit:git-checkout[1]) and the raw | |
812 | diff output (linkgit:git-diff[1]). Printing an | |
813 | ellipsis in the cases mentioned is no longer considered | |
814 | adequate and support for it is likely to be removed in the | |
815 | foreseeable future (along with the variable). | |
816 | ||
8db9307c JH |
817 | Discussion[[Discussion]] |
818 | ------------------------ | |
40dac517 BF |
819 | |
820 | More detail on the following is available from the | |
2de9b711 | 821 | link:user-manual.html#git-concepts[Git concepts chapter of the |
6998e4db | 822 | user-manual] and linkgit:gitcore-tutorial[7]. |
40dac517 | 823 | |
2de9b711 | 824 | A Git project normally consists of a working directory with a ".git" |
40dac517 BF |
825 | subdirectory at the top level. The .git directory contains, among other |
826 | things, a compressed object database representing the complete history | |
827 | of the project, an "index" file which links that history to the current | |
828 | contents of the working tree, and named pointers into that history such | |
829 | as tags and branch heads. | |
830 | ||
831 | The object database contains objects of three main types: blobs, which | |
832 | hold file data; trees, which point to blobs and other trees to build up | |
02ff6250 | 833 | directory hierarchies; and commits, which each reference a single tree |
40dac517 BF |
834 | and some number of parent commits. |
835 | ||
836 | The commit, equivalent to what other systems call a "changeset" or | |
837 | "version", represents a step in the project's history, and each parent | |
838 | represents an immediately preceding step. Commits with more than one | |
839 | parent represent merges of independent lines of development. | |
840 | ||
d5fa1f1a | 841 | All objects are named by the SHA-1 hash of their contents, normally |
40dac517 BF |
842 | written as a string of 40 hex digits. Such names are globally unique. |
843 | The entire history leading up to a commit can be vouched for by signing | |
844 | just that commit. A fourth object type, the tag, is provided for this | |
845 | purpose. | |
846 | ||
847 | When first created, objects are stored in individual files, but for | |
848 | efficiency may later be compressed together into "pack files". | |
849 | ||
850 | Named pointers called refs mark interesting points in history. A ref | |
d5fa1f1a TA |
851 | may contain the SHA-1 name of an object or the name of another ref. Refs |
852 | with names beginning `ref/head/` contain the SHA-1 name of the most | |
853 | recent commit (or "head") of a branch under development. SHA-1 names of | |
40dac517 BF |
854 | tags of interest are stored under `ref/tags/`. A special ref named |
855 | `HEAD` contains the name of the currently checked-out branch. | |
856 | ||
857 | The index file is initialized with a list of all paths and, for each | |
858 | path, a blob object and a set of attributes. The blob object represents | |
859 | the contents of the file as of the head of the current branch. The | |
860 | attributes (last modified time, size, etc.) are taken from the | |
861 | corresponding file in the working tree. Subsequent changes to the | |
862 | working tree can be found by comparing these attributes. The index may | |
863 | be updated with new content, and new commits may be created from the | |
864 | content stored in the index. | |
865 | ||
866 | The index is also capable of storing multiple entries (called "stages") | |
867 | for a given pathname. These stages are used to hold the various | |
868 | unmerged version of a file when a merge is in progress. | |
6c84e2e0 | 869 | |
7687ae98 JH |
870 | FURTHER DOCUMENTATION |
871 | --------------------- | |
872 | ||
873 | See the references in the "description" section to get started | |
2de9b711 | 874 | using Git. The following is probably more detail than necessary |
7687ae98 JH |
875 | for a first-time user. |
876 | ||
2de9b711 | 877 | The link:user-manual.html#git-concepts[Git concepts chapter of the |
7687ae98 | 878 | user-manual] and linkgit:gitcore-tutorial[7] both provide |
2de9b711 | 879 | introductions to the underlying Git architecture. |
7687ae98 JH |
880 | |
881 | See linkgit:gitworkflows[7] for an overview of recommended workflows. | |
882 | ||
883 | See also the link:howto-index.html[howto] documents for some useful | |
884 | examples. | |
885 | ||
886 | The internals are documented in the | |
48a8c26c | 887 | link:technical/api-index.html[Git API documentation]. |
7687ae98 JH |
888 | |
889 | Users migrating from CVS may also want to | |
890 | read linkgit:gitcvs-migration[7]. | |
891 | ||
892 | ||
cb22bc44 AE |
893 | Authors |
894 | ------- | |
48bb914e | 895 | Git was started by Linus Torvalds, and is currently maintained by Junio |
2de9b711 | 896 | C Hamano. Numerous contributions have come from the Git mailing list |
405869d0 | 897 | <git@vger.kernel.org>. http://www.openhub.net/p/git/contributors/summary |
6ecc01f2 JH |
898 | gives you a more complete list of contributors. |
899 | ||
900 | If you have a clone of git.git itself, the | |
d8f708f8 JK |
901 | output of linkgit:git-shortlog[1] and linkgit:git-blame[1] can show you |
902 | the authors for specific parts of the project. | |
2cf565c5 | 903 | |
c97ca277 JH |
904 | Reporting Bugs |
905 | -------------- | |
906 | ||
907 | Report bugs to the Git mailing list <git@vger.kernel.org> where the | |
908 | development and maintenance is primarily done. You do not have to be | |
c56170a0 JN |
909 | subscribed to the list to send a message there. See the list archive |
910 | at https://public-inbox.org/git for previous bug reports and other | |
911 | discussions. | |
c97ca277 | 912 | |
2caa7b8d ÆAB |
913 | Issues which are security relevant should be disclosed privately to |
914 | the Git Security mailing list <git-security@googlegroups.com>. | |
915 | ||
497c8331 CC |
916 | SEE ALSO |
917 | -------- | |
918 | linkgit:gittutorial[7], linkgit:gittutorial-2[7], | |
673151a9 | 919 | linkgit:giteveryday[7], linkgit:gitcvs-migration[7], |
497c8331 | 920 | linkgit:gitglossary[7], linkgit:gitcore-tutorial[7], |
801a011d TR |
921 | linkgit:gitcli[7], link:user-manual.html[The Git User's Manual], |
922 | linkgit:gitworkflows[7] | |
497c8331 | 923 | |
2cf565c5 DG |
924 | GIT |
925 | --- | |
9e1f0a85 | 926 | Part of the linkgit:git[1] suite |