2008-05-02 11:30:47 +08:00
|
|
|
gitcli(7)
|
2007-12-13 18:20:01 +08:00
|
|
|
=========
|
|
|
|
|
|
|
|
NAME
|
|
|
|
----
|
2014-05-22 02:52:26 +08:00
|
|
|
gitcli - Git command-line interface and conventions
|
2007-12-13 18:20:01 +08:00
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
--------
|
|
|
|
gitcli
|
|
|
|
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
-----------
|
|
|
|
|
2013-01-22 03:17:53 +08:00
|
|
|
This manual describes the convention used throughout Git CLI.
|
2008-06-26 13:16:37 +08:00
|
|
|
|
|
|
|
Many commands take revisions (most often "commits", but sometimes
|
|
|
|
"tree-ish", depending on the context and command) and paths as their
|
|
|
|
arguments. Here are the rules:
|
|
|
|
|
2022-01-17 16:21:01 +08:00
|
|
|
* Options come first and then args.
|
|
|
|
A subcommand may take dashed options (which may take their own
|
|
|
|
arguments, e.g. "--max-parents 2") and arguments. You SHOULD
|
|
|
|
give dashed options first and then arguments. Some commands may
|
|
|
|
accept dashed options after you have already gave non-option
|
|
|
|
arguments (which may make the command ambiguous), but you should
|
|
|
|
not rely on it (because eventually we may find a way to fix
|
|
|
|
these ambiguity by enforcing the "options then args" rule).
|
|
|
|
|
2008-06-26 13:16:37 +08:00
|
|
|
* Revisions come first and then paths.
|
|
|
|
E.g. in `git diff v1.0 v2.0 arch/x86 include/asm-x86`,
|
|
|
|
`v1.0` and `v2.0` are revisions and `arch/x86` and `include/asm-x86`
|
|
|
|
are paths.
|
|
|
|
|
|
|
|
* When an argument can be misunderstood as either a revision or a path,
|
docs: stop using asciidoc no-inline-literal
In asciidoc 7, backticks like `foo` produced a typographic
effect, but did not otherwise affect the syntax. In asciidoc
8, backticks introduce an "inline literal" inside which markup
is not interpreted. To keep compatibility with existing
documents, asciidoc 8 has a "no-inline-literal" attribute to
keep the old behavior. We enabled this so that the
documentation could be built on either version.
It has been several years now, and asciidoc 7 is no longer
in wide use. We can now decide whether or not we want
inline literals on their own merits, which are:
1. The source is much easier to read when the literal
contains punctuation. You can use `master~1` instead
of `master{tilde}1`.
2. They are less error-prone. Because of point (1), we
tend to make mistakes and forget the extra layer of
quoting.
This patch removes the no-inline-literal attribute from the
Makefile and converts every use of backticks in the
documentation to an inline literal (they must be cleaned up,
or the example above would literally show "{tilde}" in the
output).
Problematic sites were found by grepping for '`.*[{\\]' and
examined and fixed manually. The results were then verified
by comparing the output of "html2text" on the set of
generated html pages. Doing so revealed that in addition to
making the source more readable, this patch fixes several
formatting bugs:
- HTML rendering used the ellipsis character instead of
literal "..." in code examples (like "git log A...B")
- some code examples used the right-arrow character
instead of '->' because they failed to quote
- api-config.txt did not quote tilde, and the resulting
HTML contained a bogus snippet like:
<tt><sub></tt> foo <tt></sub>bar</tt>
which caused some parsers to choke and omit whole
sections of the page.
- git-commit.txt confused ``foo`` (backticks inside a
literal) with ``foo'' (matched double-quotes)
- mentions of `A U Thor <author@example.com>` used to
erroneously auto-generate a mailto footnote for
author@example.com
- the description of --word-diff=plain incorrectly showed
the output as "[-removed-] and {added}", not "{+added+}".
- using "prime" notation like:
commit `C` and its replacement `C'`
confused asciidoc into thinking that everything between
the first backtick and the final apostrophe were meant
to be inside matched quotes
- asciidoc got confused by the escaping of some of our
asterisks. In particular,
`credential.\*` and `credential.<url>.\*`
properly escaped the asterisk in the first case, but
literally passed through the backslash in the second
case.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-26 16:51:57 +08:00
|
|
|
they can be disambiguated by placing `--` between them.
|
|
|
|
E.g. `git diff -- HEAD` is, "I have a file called HEAD in my work
|
2008-06-26 13:16:37 +08:00
|
|
|
tree. Please show changes between the version I staged in the index
|
2014-02-06 06:19:43 +08:00
|
|
|
and what I have in the work tree for that file", not "show difference
|
2008-06-26 13:16:37 +08:00
|
|
|
between the HEAD commit and the work tree as a whole". You can say
|
docs: stop using asciidoc no-inline-literal
In asciidoc 7, backticks like `foo` produced a typographic
effect, but did not otherwise affect the syntax. In asciidoc
8, backticks introduce an "inline literal" inside which markup
is not interpreted. To keep compatibility with existing
documents, asciidoc 8 has a "no-inline-literal" attribute to
keep the old behavior. We enabled this so that the
documentation could be built on either version.
It has been several years now, and asciidoc 7 is no longer
in wide use. We can now decide whether or not we want
inline literals on their own merits, which are:
1. The source is much easier to read when the literal
contains punctuation. You can use `master~1` instead
of `master{tilde}1`.
2. They are less error-prone. Because of point (1), we
tend to make mistakes and forget the extra layer of
quoting.
This patch removes the no-inline-literal attribute from the
Makefile and converts every use of backticks in the
documentation to an inline literal (they must be cleaned up,
or the example above would literally show "{tilde}" in the
output).
Problematic sites were found by grepping for '`.*[{\\]' and
examined and fixed manually. The results were then verified
by comparing the output of "html2text" on the set of
generated html pages. Doing so revealed that in addition to
making the source more readable, this patch fixes several
formatting bugs:
- HTML rendering used the ellipsis character instead of
literal "..." in code examples (like "git log A...B")
- some code examples used the right-arrow character
instead of '->' because they failed to quote
- api-config.txt did not quote tilde, and the resulting
HTML contained a bogus snippet like:
<tt><sub></tt> foo <tt></sub>bar</tt>
which caused some parsers to choke and omit whole
sections of the page.
- git-commit.txt confused ``foo`` (backticks inside a
literal) with ``foo'' (matched double-quotes)
- mentions of `A U Thor <author@example.com>` used to
erroneously auto-generate a mailto footnote for
author@example.com
- the description of --word-diff=plain incorrectly showed
the output as "[-removed-] and {added}", not "{+added+}".
- using "prime" notation like:
commit `C` and its replacement `C'`
confused asciidoc into thinking that everything between
the first backtick and the final apostrophe were meant
to be inside matched quotes
- asciidoc got confused by the escaping of some of our
asterisks. In particular,
`credential.\*` and `credential.<url>.\*`
properly escaped the asterisk in the first case, but
literally passed through the backslash in the second
case.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-26 16:51:57 +08:00
|
|
|
`git diff HEAD --` to ask for the latter.
|
2008-06-26 13:16:37 +08:00
|
|
|
|
2013-01-22 03:17:53 +08:00
|
|
|
* Without disambiguating `--`, Git makes a reasonable guess, but errors
|
2008-06-26 13:16:37 +08:00
|
|
|
out and asking you to disambiguate when ambiguous. E.g. if you have a
|
|
|
|
file called HEAD in your work tree, `git diff HEAD` is ambiguous, and
|
docs: stop using asciidoc no-inline-literal
In asciidoc 7, backticks like `foo` produced a typographic
effect, but did not otherwise affect the syntax. In asciidoc
8, backticks introduce an "inline literal" inside which markup
is not interpreted. To keep compatibility with existing
documents, asciidoc 8 has a "no-inline-literal" attribute to
keep the old behavior. We enabled this so that the
documentation could be built on either version.
It has been several years now, and asciidoc 7 is no longer
in wide use. We can now decide whether or not we want
inline literals on their own merits, which are:
1. The source is much easier to read when the literal
contains punctuation. You can use `master~1` instead
of `master{tilde}1`.
2. They are less error-prone. Because of point (1), we
tend to make mistakes and forget the extra layer of
quoting.
This patch removes the no-inline-literal attribute from the
Makefile and converts every use of backticks in the
documentation to an inline literal (they must be cleaned up,
or the example above would literally show "{tilde}" in the
output).
Problematic sites were found by grepping for '`.*[{\\]' and
examined and fixed manually. The results were then verified
by comparing the output of "html2text" on the set of
generated html pages. Doing so revealed that in addition to
making the source more readable, this patch fixes several
formatting bugs:
- HTML rendering used the ellipsis character instead of
literal "..." in code examples (like "git log A...B")
- some code examples used the right-arrow character
instead of '->' because they failed to quote
- api-config.txt did not quote tilde, and the resulting
HTML contained a bogus snippet like:
<tt><sub></tt> foo <tt></sub>bar</tt>
which caused some parsers to choke and omit whole
sections of the page.
- git-commit.txt confused ``foo`` (backticks inside a
literal) with ``foo'' (matched double-quotes)
- mentions of `A U Thor <author@example.com>` used to
erroneously auto-generate a mailto footnote for
author@example.com
- the description of --word-diff=plain incorrectly showed
the output as "[-removed-] and {added}", not "{+added+}".
- using "prime" notation like:
commit `C` and its replacement `C'`
confused asciidoc into thinking that everything between
the first backtick and the final apostrophe were meant
to be inside matched quotes
- asciidoc got confused by the escaping of some of our
asterisks. In particular,
`credential.\*` and `credential.<url>.\*`
properly escaped the asterisk in the first case, but
literally passed through the backslash in the second
case.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-26 16:51:57 +08:00
|
|
|
you have to say either `git diff HEAD --` or `git diff -- HEAD` to
|
2008-06-26 13:16:37 +08:00
|
|
|
disambiguate.
|
2019-08-06 22:40:30 +08:00
|
|
|
|
|
|
|
* Because `--` disambiguates revisions and paths in some commands, it
|
|
|
|
cannot be used for those commands to separate options and revisions.
|
|
|
|
You can use `--end-of-options` for this (it also works for commands
|
|
|
|
that do not distinguish between revisions in paths, in which case it
|
|
|
|
is simply an alias for `--`).
|
2012-09-11 03:47:38 +08:00
|
|
|
+
|
2008-06-26 13:16:37 +08:00
|
|
|
When writing a script that is expected to handle random user-input, it is
|
|
|
|
a good practice to make it explicit which arguments are which by placing
|
docs: stop using asciidoc no-inline-literal
In asciidoc 7, backticks like `foo` produced a typographic
effect, but did not otherwise affect the syntax. In asciidoc
8, backticks introduce an "inline literal" inside which markup
is not interpreted. To keep compatibility with existing
documents, asciidoc 8 has a "no-inline-literal" attribute to
keep the old behavior. We enabled this so that the
documentation could be built on either version.
It has been several years now, and asciidoc 7 is no longer
in wide use. We can now decide whether or not we want
inline literals on their own merits, which are:
1. The source is much easier to read when the literal
contains punctuation. You can use `master~1` instead
of `master{tilde}1`.
2. They are less error-prone. Because of point (1), we
tend to make mistakes and forget the extra layer of
quoting.
This patch removes the no-inline-literal attribute from the
Makefile and converts every use of backticks in the
documentation to an inline literal (they must be cleaned up,
or the example above would literally show "{tilde}" in the
output).
Problematic sites were found by grepping for '`.*[{\\]' and
examined and fixed manually. The results were then verified
by comparing the output of "html2text" on the set of
generated html pages. Doing so revealed that in addition to
making the source more readable, this patch fixes several
formatting bugs:
- HTML rendering used the ellipsis character instead of
literal "..." in code examples (like "git log A...B")
- some code examples used the right-arrow character
instead of '->' because they failed to quote
- api-config.txt did not quote tilde, and the resulting
HTML contained a bogus snippet like:
<tt><sub></tt> foo <tt></sub>bar</tt>
which caused some parsers to choke and omit whole
sections of the page.
- git-commit.txt confused ``foo`` (backticks inside a
literal) with ``foo'' (matched double-quotes)
- mentions of `A U Thor <author@example.com>` used to
erroneously auto-generate a mailto footnote for
author@example.com
- the description of --word-diff=plain incorrectly showed
the output as "[-removed-] and {added}", not "{+added+}".
- using "prime" notation like:
commit `C` and its replacement `C'`
confused asciidoc into thinking that everything between
the first backtick and the final apostrophe were meant
to be inside matched quotes
- asciidoc got confused by the escaping of some of our
asterisks. In particular,
`credential.\*` and `credential.<url>.\*`
properly escaped the asterisk in the first case, but
literally passed through the backslash in the second
case.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-26 16:51:57 +08:00
|
|
|
disambiguating `--` at appropriate places.
|
2008-06-26 13:16:37 +08:00
|
|
|
|
2012-09-08 04:49:15 +08:00
|
|
|
* Many commands allow wildcards in paths, but you need to protect
|
|
|
|
them from getting globbed by the shell. These two mean different
|
|
|
|
things:
|
|
|
|
+
|
|
|
|
--------------------------------
|
2019-04-25 17:45:58 +08:00
|
|
|
$ git restore *.c
|
|
|
|
$ git restore \*.c
|
2012-09-08 04:49:15 +08:00
|
|
|
--------------------------------
|
|
|
|
+
|
|
|
|
The former lets your shell expand the fileglob, and you are asking
|
|
|
|
the dot-C files in your working tree to be overwritten with the version
|
|
|
|
in the index. The latter passes the `*.c` to Git, and you are asking
|
|
|
|
the paths in the index that match the pattern to be checked out to your
|
|
|
|
working tree. After running `git add hello.c; rm hello.c`, you will _not_
|
|
|
|
see `hello.c` in your working tree with the former, but with the latter
|
|
|
|
you will.
|
|
|
|
|
2013-10-16 05:57:42 +08:00
|
|
|
* Just as the filesystem '.' (period) refers to the current directory,
|
|
|
|
using a '.' as a repository name in Git (a dot-repository) is a relative
|
|
|
|
path and means your current repository.
|
2012-09-08 04:49:15 +08:00
|
|
|
|
2008-06-26 13:16:37 +08:00
|
|
|
Here are the rules regarding the "flags" that you should follow when you are
|
2013-01-22 03:17:53 +08:00
|
|
|
scripting Git:
|
2007-12-13 18:20:01 +08:00
|
|
|
|
2022-01-17 16:21:01 +08:00
|
|
|
* It's preferred to use the non-dashed form of Git commands, which means that
|
2009-03-15 19:30:52 +08:00
|
|
|
you should prefer `git foo` to `git-foo`.
|
2007-12-13 18:20:01 +08:00
|
|
|
|
2022-01-17 16:21:01 +08:00
|
|
|
* Splitting short options to separate words (prefer `git foo -a -b`
|
2009-03-15 19:30:52 +08:00
|
|
|
to `git foo -ab`, the latter may not even work).
|
2007-12-13 18:20:01 +08:00
|
|
|
|
2022-01-17 16:21:01 +08:00
|
|
|
* When a command-line option takes an argument, use the 'stuck' form. In
|
2009-03-15 19:30:52 +08:00
|
|
|
other words, write `git foo -oArg` instead of `git foo -o Arg` for short
|
|
|
|
options, and `git foo --long-opt=Arg` instead of `git foo --long-opt Arg`
|
2007-12-13 18:20:01 +08:00
|
|
|
for long options. An option that takes optional option-argument must be
|
2013-10-31 19:08:28 +08:00
|
|
|
written in the 'stuck' form.
|
2007-12-13 18:20:01 +08:00
|
|
|
|
2022-01-17 16:21:01 +08:00
|
|
|
* When you give a revision parameter to a command, make sure the parameter is
|
2007-12-13 18:20:01 +08:00
|
|
|
not ambiguous with a name of a file in the work tree. E.g. do not write
|
2009-03-15 19:30:52 +08:00
|
|
|
`git log -1 HEAD` but write `git log -1 HEAD --`; the former will not work
|
2007-12-13 18:20:01 +08:00
|
|
|
if you happen to have a file called `HEAD` in the work tree.
|
|
|
|
|
2022-01-17 16:21:01 +08:00
|
|
|
* Many commands allow a long option `--option` to be abbreviated
|
2012-08-17 14:16:22 +08:00
|
|
|
only to their unique prefix (e.g. if there is no other option
|
2013-11-20 09:34:40 +08:00
|
|
|
whose name begins with `opt`, you may be able to spell `--opt` to
|
|
|
|
invoke the `--option` flag), but you should fully spell them out
|
2012-08-17 14:16:22 +08:00
|
|
|
when writing your scripts; later versions of Git may introduce a
|
2013-11-20 09:34:40 +08:00
|
|
|
new option whose name shares the same prefix, e.g. `--optimize`,
|
2012-08-17 14:16:22 +08:00
|
|
|
to make a short prefix that used to be unique no longer unique.
|
|
|
|
|
2007-12-13 18:20:01 +08:00
|
|
|
|
2008-06-26 13:16:37 +08:00
|
|
|
ENHANCED OPTION PARSER
|
|
|
|
----------------------
|
2013-01-22 03:17:53 +08:00
|
|
|
From the Git 1.5.4 series and further, many Git commands (not all of them at the
|
2007-12-13 18:20:01 +08:00
|
|
|
time of the writing though) come with an enhanced option parser.
|
|
|
|
|
2012-10-05 01:13:49 +08:00
|
|
|
Here is a list of the facilities provided by this option parser.
|
2007-12-13 18:20:01 +08:00
|
|
|
|
|
|
|
|
|
|
|
Magic Options
|
|
|
|
~~~~~~~~~~~~~
|
|
|
|
Commands which have the enhanced option parser activated all understand a
|
2014-05-22 02:52:26 +08:00
|
|
|
couple of magic command-line options:
|
2007-12-13 18:20:01 +08:00
|
|
|
|
|
|
|
-h::
|
|
|
|
gives a pretty printed usage of the command.
|
|
|
|
+
|
|
|
|
---------------------------------------------
|
|
|
|
$ git describe -h
|
2018-05-25 04:11:39 +08:00
|
|
|
usage: git describe [<options>] <commit-ish>*
|
|
|
|
or: git describe [<options>] --dirty
|
2007-12-13 18:20:01 +08:00
|
|
|
|
|
|
|
--contains find the tag that comes after the commit
|
|
|
|
--debug debug search strategy on stderr
|
2013-02-25 13:34:14 +08:00
|
|
|
--all use any ref
|
|
|
|
--tags use any tag, even unannotated
|
|
|
|
--long always use long format
|
|
|
|
--abbrev[=<n>] use <n> digits to display SHA-1s
|
2007-12-13 18:20:01 +08:00
|
|
|
---------------------------------------------
|
2020-02-28 00:10:20 +08:00
|
|
|
+
|
|
|
|
Note that some subcommand (e.g. `git grep`) may behave differently
|
|
|
|
when there are things on the command line other than `-h`, but `git
|
|
|
|
subcmd -h` without anything else on the command line is meant to
|
|
|
|
consistently give the usage.
|
2007-12-13 18:20:01 +08:00
|
|
|
|
|
|
|
--help-all::
|
2013-01-22 03:17:53 +08:00
|
|
|
Some Git commands take options that are only used for plumbing or that
|
2007-12-13 18:20:01 +08:00
|
|
|
are deprecated, and such options are hidden from the default usage. This
|
|
|
|
option gives the full list of options.
|
|
|
|
|
|
|
|
|
|
|
|
Negating options
|
|
|
|
~~~~~~~~~~~~~~~~
|
2009-03-15 19:30:52 +08:00
|
|
|
Options with long option names can be negated by prefixing `--no-`. For
|
|
|
|
example, `git branch` has the option `--track` which is 'on' by default. You
|
|
|
|
can use `--no-track` to override that behaviour. The same goes for `--color`
|
|
|
|
and `--no-color`.
|
2007-12-13 18:20:01 +08:00
|
|
|
|
|
|
|
|
|
|
|
Aggregating short options
|
|
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
Commands that support the enhanced option parser allow you to aggregate short
|
2009-03-15 19:30:52 +08:00
|
|
|
options. This means that you can for example use `git rm -rf` or
|
|
|
|
`git clean -fdx`.
|
2007-12-13 18:20:01 +08:00
|
|
|
|
|
|
|
|
2012-10-05 01:13:49 +08:00
|
|
|
Abbreviating long options
|
|
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
Commands that support the enhanced option parser accepts unique
|
|
|
|
prefix of a long option as if it is fully spelled out, but use this
|
|
|
|
with a caution. For example, `git commit --amen` behaves as if you
|
|
|
|
typed `git commit --amend`, but that is true only until a later version
|
|
|
|
of Git introduces another option that shares the same prefix,
|
2013-11-20 09:34:40 +08:00
|
|
|
e.g. `git commit --amenity` option.
|
2012-10-05 01:13:49 +08:00
|
|
|
|
|
|
|
|
2007-12-13 18:20:01 +08:00
|
|
|
Separating argument from the option
|
|
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
You can write the mandatory option parameter to an option as a separate
|
|
|
|
word on the command line. That means that all the following uses work:
|
|
|
|
|
|
|
|
----------------------------
|
|
|
|
$ git foo --long-opt=Arg
|
|
|
|
$ git foo --long-opt Arg
|
|
|
|
$ git foo -oArg
|
|
|
|
$ git foo -o Arg
|
|
|
|
----------------------------
|
|
|
|
|
2008-01-08 05:43:27 +08:00
|
|
|
However, this is *NOT* allowed for switches with an optional value, where the
|
2013-10-31 19:08:28 +08:00
|
|
|
'stuck' form must be used:
|
2007-12-13 18:20:01 +08:00
|
|
|
----------------------------
|
|
|
|
$ git describe --abbrev HEAD # correct
|
|
|
|
$ git describe --abbrev=10 HEAD # correct
|
|
|
|
$ git describe --abbrev 10 HEAD # NOT WHAT YOU MEANT
|
|
|
|
----------------------------
|
|
|
|
|
|
|
|
|
2008-07-01 22:02:40 +08:00
|
|
|
NOTES ON FREQUENTLY CONFUSED OPTIONS
|
|
|
|
------------------------------------
|
|
|
|
|
|
|
|
Many commands that can work on files in the working tree
|
|
|
|
and/or in the index can take `--cached` and/or `--index`
|
|
|
|
options. Sometimes people incorrectly think that, because
|
|
|
|
the index was originally called cache, these two are
|
|
|
|
synonyms. They are *not* -- these two options mean very
|
|
|
|
different things.
|
|
|
|
|
|
|
|
* The `--cached` option is used to ask a command that
|
|
|
|
usually works on files in the working tree to *only* work
|
|
|
|
with the index. For example, `git grep`, when used
|
|
|
|
without a commit to specify from which commit to look for
|
|
|
|
strings in, usually works on files in the working tree,
|
|
|
|
but with the `--cached` option, it looks for strings in
|
|
|
|
the index.
|
|
|
|
|
|
|
|
* The `--index` option is used to ask a command that
|
|
|
|
usually works on files in the working tree to *also*
|
|
|
|
affect the index. For example, `git stash apply` usually
|
2017-06-18 06:30:50 +08:00
|
|
|
merges changes recorded in a stash entry to the working tree,
|
2008-07-01 22:02:40 +08:00
|
|
|
but with the `--index` option, it also merges changes to
|
|
|
|
the index as well.
|
|
|
|
|
|
|
|
`git apply` command can be used with `--cached` and
|
|
|
|
`--index` (but not at the same time). Usually the command
|
|
|
|
only affects the files in the working tree, but with
|
|
|
|
`--index`, it patches both the files and their index
|
|
|
|
entries, and with `--cached`, it modifies only the index
|
|
|
|
entries.
|
|
|
|
|
2019-12-03 03:26:18 +08:00
|
|
|
See also https://lore.kernel.org/git/7v64clg5u9.fsf@assigned-by-dhcp.cox.net/ and
|
|
|
|
https://lore.kernel.org/git/7vy7ej9g38.fsf@gitster.siamese.dyndns.org/ for further
|
2008-07-01 22:02:40 +08:00
|
|
|
information.
|
|
|
|
|
2019-04-25 17:45:45 +08:00
|
|
|
Some other commands that also work on files in the working tree and/or
|
|
|
|
in the index can take `--staged` and/or `--worktree`.
|
|
|
|
|
|
|
|
* `--staged` is exactly like `--cached`, which is used to ask a
|
|
|
|
command to only work on the index, not the working tree.
|
|
|
|
|
|
|
|
* `--worktree` is the opposite, to ask a command to work on the
|
|
|
|
working tree only, not the index.
|
|
|
|
|
|
|
|
* The two options can be specified together to ask a command to work
|
|
|
|
on both the index and the working tree.
|
|
|
|
|
2007-12-13 18:20:01 +08:00
|
|
|
GIT
|
|
|
|
---
|
2008-06-06 15:07:32 +08:00
|
|
|
Part of the linkgit:git[1] suite
|