git/Documentation/git.txt, branch v2.22.2

Document that 'git -C ""' works and doesn't change directory

2019-07-01T17:42:49Z

It's been behaving so since 6a536e2076 (git: treat "git -C ''" as a no-op when is empty, 2015-03-06). Signed-off-by: SZEDER Gábor Signed-off-by: Junio C Hamano

trace2: document the supported values of GIT_TRACE2* env variables

2019-05-28T17:20:36Z

The descriptions of the GIT_TRACE2* environment variables link to the technical docs for further details on the supported values. However, a link like this only really works if the docs are viewed in a browser and the full documentation is available. OTOH, in 'man git' there are no links to conveniently click on, and distro-shipped git packages tend to include only the man pages, while the technical docs and the docs in html format are in a separate 'git-doc' package. So let's describe the supported values to make the manpage more self-contained, but still keep the references to the technical docs because the details of the SID, and the JSON and perf output formats are definitely beyond the scope of 'man git'. Signed-off-by: SZEDER Gábor Signed-off-by: Junio C Hamano

trace2: rename environment variables to GIT_TRACE2*

2019-05-28T17:20:34Z

For an environment variable that is supposed to be set by users, the GIT_TR2* env vars are just too unclear, inconsistent, and ugly. Most of the established GIT_* environment variables don't use abbreviations, and in case of the few that do (GIT_DIR, GIT_COMMON_DIR, GIT_DIFF_OPTS) it's quite obvious what the abbreviations (DIR and OPTS) stand for. But what does TR stand for? Track, traditional, trailer, transaction, transfer, transformation, transition, translation, transplant, transport, traversal, tree, trigger, truncate, trust, or ...?! The trace2 facility, as the '2' suffix in its name suggests, is supposed to eventually supercede Git's original trace facility. It's reasonable to expect that the corresponding environment variables follow suit, and after the original GIT_TRACE variables they are called GIT_TRACE2; there is no such thing is 'GIT_TR'. All trace2-specific config variables are, very sensibly, in the 'trace2' section, not in 'tr2'. OTOH, we don't gain anything at all by omitting the last three characters of "trace" from the names of these environment variables. So let's rename all GIT_TR2* environment variables to GIT_TRACE2*, before they make their way into a stable release. Signed-off-by: SZEDER Gábor Signed-off-by: Junio C Hamano

trace2: add variable description to git.txt

2019-05-13T13:54:02Z

Documentation/technical/api-trace2.txt contains the full details of the trace2 API and the GIT_TR2* environment variables. However, most environment variables are included in Documentation/git.txt, including the GIT_TRACE* variables. Add a brief description of the GIT_TR2* variables with links to the full technical details. The biggest difference from the original variables is that we can specify a Unix Domain Socket. Mention this difference, but leave the details to the technical documents. Reported-by: Szeder Gábor Signed-off-by: Derrick Stolee Signed-off-by: Junio C Hamano

git.txt: remove empty line before list continuation

2019-03-07T00:25:32Z

This patch is a no-op for Asciidoctor, but makes AsciiDoc render this as intended. Signed-off-by: Martin Ågren Signed-off-by: Junio C Hamano

Merge branch 'ah/doc-updates'

2018-10-30T06:43:47Z

Doc updates. * ah/doc-updates: doc: fix formatting in git-update-ref doc: fix indentation of listing blocks in gitweb.conf.txt doc: fix descripion for 'git tag --format' doc: fix inappropriate monospace formatting doc: fix ASCII art tab spacing doc: clarify boundaries of 'git worktree list --porcelain'

doc: fix inappropriate monospace formatting

2018-10-23T03:23:09Z

Signed-off-by: Andreas Heiduk Signed-off-by: Junio C Hamano

Merge branch 'ma/mailing-list-address-in-git-help'

2018-10-16T07:16:07Z

Doc update. * ma/mailing-list-address-in-git-help: git doc: direct bug reporters to mailing list archive

git doc: direct bug reporters to mailing list archive

2018-09-29T18:32:04Z

The mailing list archive can help a user encountering a bug to tell whether a recent regression has already been reported and whether a longstanding bug has already had some discussion to start their thinking. Based-on-patch-by: Martin Ågren Improved-by: Junio C Hamano Improved-by: Jonathan Nieder Signed-off-by: Jonathan Nieder Signed-off-by: Junio C Hamano

Doc: use `--type=bool` instead of `--bool`

2018-09-20T18:52:40Z

After fb0dc3bac1 (builtin/config.c: support `--type=` as preferred alias for `--`, 2018-04-18) we have a more modern way of spelling `--bool`. Update all instances except those that explicitly document the "historical options" in git-config.txt. The other old-style type-specifiers already seem to be gone except for in that list of historical options. Tweak the grammar a little in config.txt while we are there. Signed-off-by: Martin Ågren Signed-off-by: Junio C Hamano