<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/Documentation/git-var.adoc, branch jch</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=jch</id>
<link rel='self' href='https://git.shady.money/git/atom?h=jch'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2026-04-06T16:57:07Z</updated>
<entry>
<title>doc: replace git config --list/-l with `list`</title>
<updated>2026-04-06T16:57:07Z</updated>
<author>
<name>Kristoffer Haugsbakk</name>
<email>code@khaugsbakk.name</email>
</author>
<published>2026-04-05T10:31:59Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=5bdb9883bda41024e3c47f1cddf69977d82fe3a9'/>
<id>urn:sha1:5bdb9883bda41024e3c47f1cddf69977d82fe3a9</id>
<content type='text'>
Replace uses of `git config --list` (short or long) with the subcommand
`list` since `--list` is deprecated.

We will change the “man page” phrasing in gitcvs-migration(7) in the
next commit, since we are already visiting that sentence. But note
that we leave the “man page” phrasing in the sentence that we touch in
gittutorial(7) since it’s a tutorial and not a manual page. We can be
more wordy in a tutorial context.

Signed-off-by: Kristoffer Haugsbakk &lt;code@khaugsbakk.name&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>git-var doc: fix usage of $ENV_VAR vs ENV_VAR</title>
<updated>2025-05-12T16:25:27Z</updated>
<author>
<name>Jean-Noël Avila</name>
<email>jn.avila@free.fr</email>
</author>
<published>2025-05-10T12:33:17Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=20e4e9ad0b72be0a4ccf9300f51c383c03beec97'/>
<id>urn:sha1:20e4e9ad0b72be0a4ccf9300f51c383c03beec97</id>
<content type='text'>
When refering to environment variables in the documentation, use the
ENV_VARIABLE format instead of $ENV_VARIABLE. The latter is used in the
documentation to refer to the actual value of the variable, not the name
of the variable.

Signed-off-by: Jean-Noël Avila &lt;jn.avila@free.fr&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>git-{var,write-tree} docs: update mark-up of synopsis option descriptions</title>
<updated>2025-05-12T16:25:26Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2025-05-10T12:33:15Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=914c549ac161c3393dd760be5af4d290620a27e8'/>
<id>urn:sha1:914c549ac161c3393dd760be5af4d290620a27e8</id>
<content type='text'>
To unify mark-up used in our documentation to a newer convention,
started by 22293895 (doc: apply synopsis simplification on git-clone
and git-init, 2024-09-24), update the documentation for 'git var' and
'git write-tree' to

 * use [synopsis], not [verse] in the SYNOPSIS section
 * enclose `--option=&lt;value&gt;` in backquotes

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
Helped-by: Jean-Noël Avila &lt;jn.avila@free.fr&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>doc: use .adoc extension for AsciiDoc files</title>
<updated>2025-01-21T20:56:06Z</updated>
<author>
<name>brian m. carlson</name>
<email>sandals@crustytoothpaste.net</email>
</author>
<published>2025-01-20T01:56:02Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=1f010d6bdf756129db13d1367c888aa4153f6d87'/>
<id>urn:sha1:1f010d6bdf756129db13d1367c888aa4153f6d87</id>
<content type='text'>
We presently use the ".txt" extension for our AsciiDoc files.  While not
wrong, most editors do not associate this extension with AsciiDoc,
meaning that contributors don't get automatic editor functionality that
could be useful, such as syntax highlighting and prose linting.

It is much more common to use the ".adoc" extension for AsciiDoc files,
since this helps editors automatically detect files and also allows
various forges to provide rich (HTML-like) rendering.  Let's do that
here, renaming all of the files and updating the includes where
relevant.  Adjust the various build scripts and makefiles to use the new
extension as well.

Note that this should not result in any user-visible changes to the
documentation.

Signed-off-by: brian m. carlson &lt;sandals@crustytoothpaste.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
</feed>
