<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/Documentation/git-daemon.txt, branch v2.20.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.20.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.20.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2018-02-05T18:30:44Z</updated>
<entry>
<title>daemon: add --log-destination=(stderr|syslog|none)</title>
<updated>2018-02-05T18:30:44Z</updated>
<author>
<name>Lucas Werkmeister</name>
<email>mail@lucaswerkmeister.de</email>
</author>
<published>2018-02-04T18:30:37Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=0c591cacba00a36af797fa3b6c4a4f12d342be86'/>
<id>urn:sha1:0c591cacba00a36af797fa3b6c4a4f12d342be86</id>
<content type='text'>
This new option can be used to override the implicit --syslog of
--inetd, or to disable all logging. (While --detach also implies
--syslog, --log-destination=stderr with --detach is useless since
--detach disassociates the process from the original stderr.) --syslog
is retained as an alias for --log-destination=syslog.

--log-destination always overrides implicit --syslog regardless of
option order. This is different than the “last one wins” logic that
applies to some implicit options elsewhere in Git, but should hopefully
be less confusing. (I also don’t know if *all* implicit options in Git
follow “last one wins”.)

The combination of --inetd with --log-destination=stderr is useful, for
instance, when running `git daemon` as an instanced systemd service
(with associated socket unit). In this case, log messages sent via
syslog are received by the journal daemon, but run the risk of being
processed at a time when the `git daemon` process has already exited
(especially if the process was very short-lived, e.g. due to client
error), so that the journal daemon can no longer read its cgroup and
attach the message to the correct systemd unit (see systemd/systemd#2913
[1]). Logging to stderr instead can solve this problem, because systemd
can connect stderr directly to the journal daemon, which then already
knows which unit is associated with this stream.

[1]: https://github.com/systemd/systemd/issues/2913

Helped-by: Ævar Arnfjörð Bjarmason &lt;avarab@gmail.com&gt;
Helped-by: Junio C Hamano &lt;gitster@pobox.com&gt;
Helped-by: Eric Sunshine &lt;sunshine@sunshineco.com&gt;
Signed-off-by: Lucas Werkmeister &lt;mail@lucaswerkmeister.de&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>doc: typeset HEAD and variants as literal</title>
<updated>2016-06-28T15:36:45Z</updated>
<author>
<name>Matthieu Moy</name>
<email>Matthieu.Moy@imag.fr</email>
</author>
<published>2016-06-28T11:40:15Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=661c3e9bc064564a492281364413dc805eaddf95'/>
<id>urn:sha1:661c3e9bc064564a492281364413dc805eaddf95</id>
<content type='text'>
This is an application of the newly added CodingGuidelines to HEAD and
variants like FETCH_HEAD. It was obtained with:

  perl -pi -e "s/'([A-Z_]*HEAD)'/\`\$1\`/g" *.txt

Signed-off-by: Matthieu Moy &lt;Matthieu.Moy@imag.fr&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>doc: typeset long command-line options as literal</title>
<updated>2016-06-28T15:36:45Z</updated>
<author>
<name>Matthieu Moy</name>
<email>Matthieu.Moy@imag.fr</email>
</author>
<published>2016-06-28T11:40:11Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=bcf9626a71a0d90be65acc265ad0ec488d95d6ed'/>
<id>urn:sha1:bcf9626a71a0d90be65acc265ad0ec488d95d6ed</id>
<content type='text'>
Similarly to the previous commit, use backquotes instead of
forward-quotes, for long options.

This was obtained with:

  perl -pi -e "s/'(--[a-z][a-z=&lt;&gt;-]*)'/\`\$1\`/g" *.txt

and manual tweak to remove false positive in ascii-art (o'--o'--o' to
describe rewritten history).

Signed-off-by: Matthieu Moy &lt;Matthieu.Moy@imag.fr&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>doc: more consistency in environment variables format</title>
<updated>2016-06-08T19:04:37Z</updated>
<author>
<name>Tom Russello</name>
<email>tom.russello@grenoble-inp.org</email>
</author>
<published>2016-06-07T22:35:07Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=47d81b5c7a3e7737d26b877a5cfebb772d75fa12'/>
<id>urn:sha1:47d81b5c7a3e7737d26b877a5cfebb772d75fa12</id>
<content type='text'>
Wrap with backticks (monospaced font) unwrapped or single-quotes wrapped
(italic type) environment variables which are followed by the word
"environment". It was obtained with:

perl -pi -e "s/\'?(\\\$?[0-9A-Z\_]+)\'?(?= environment ?)/\`\1\`/g" *.txt

One of the main purposes is to stick to the CodingGuidelines as possible so
that people writting new documentation by mimicking the existing are more likely
to have it right (even if they didn't read the CodingGuidelines).

Signed-off-by: Tom Russello &lt;tom.russello@grenoble-inp.org&gt;
Signed-off-by: Erwan Mathoniere &lt;erwan.mathoniere@grenoble-inp.org&gt;
Signed-off-by: Samuel Groot &lt;samuel.groot@grenoble-inp.org&gt;
Signed-off-by: Matthieu Moy &lt;matthieu.moy@grenoble-inp.fr&gt;
Reviewed-by: Matthieu Moy &lt;Matthieu.Moy@imag.fr&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Documentation: use "command-line" when used as a compound adjective, and fix other minor grammatical issues</title>
<updated>2014-05-21T20:57:10Z</updated>
<author>
<name>Jason St. John</name>
<email>jstjohn@purdue.edu</email>
</author>
<published>2014-05-21T18:52:26Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=06ab60c06606613f238f3154cb27cb22d9723967'/>
<id>urn:sha1:06ab60c06606613f238f3154cb27cb22d9723967</id>
<content type='text'>
Signed-off-by: Jason St. John &lt;jstjohn@purdue.edu&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>documentation: trivial style cleanups</title>
<updated>2013-05-17T19:09:21Z</updated>
<author>
<name>Felipe Contreras</name>
<email>felipe.contreras@gmail.com</email>
</author>
<published>2013-05-09T01:16:55Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=0460ed2c93d78c753242f835c441f320f792ac54'/>
<id>urn:sha1:0460ed2c93d78c753242f835c441f320f792ac54</id>
<content type='text'>
White-spaces, missing braces, standardize --[no-]foo.

Signed-off-by: Felipe Contreras &lt;felipe.contreras@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'jk/daemon-user-doc'</title>
<updated>2013-04-18T18:47:23Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2013-04-18T18:47:23Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=8dd28584a5fe737ca373315f47055f3df2260606'/>
<id>urn:sha1:8dd28584a5fe737ca373315f47055f3df2260606</id>
<content type='text'>
Document where the configuration is read by the git-daemon when its --user
option is used.

* jk/daemon-user-doc:
  doc: clarify that "git daemon --user=&lt;user&gt;" option does not export HOME=~user
</content>
</entry>
<entry>
<title>doc: clarify that "git daemon --user=&lt;user&gt;" option does not export HOME=~user</title>
<updated>2013-04-12T17:29:06Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2013-04-12T16:08:31Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=714d25868f156e0969eb8a47e6a1bf3df9c17a5d'/>
<id>urn:sha1:714d25868f156e0969eb8a47e6a1bf3df9c17a5d</id>
<content type='text'>
The fact that we don't set $HOME may confuse admins who expect
~&lt;user&gt;/.gitconfig to be used, because that is not what we try to
read.  And worse, since 96b9e0e3, a git-daemon started by root is
likely to fail to run at all, as the user we switch to generally
cannot read ~root.

Signed-off-by: Jeff King &lt;peff@peff.net&gt;
Helped-by: W. Trevor King &lt;wking@tremily.us&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Documentation: the name of the system is 'Git', not 'git'</title>
<updated>2013-02-01T21:53:33Z</updated>
<author>
<name>Thomas Ackermann</name>
<email>th.acker@arcor.de</email>
</author>
<published>2013-01-21T19:17:53Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=2de9b71138171dca7279db3b3fe67e868c76d921'/>
<id>urn:sha1:2de9b71138171dca7279db3b3fe67e868c76d921</id>
<content type='text'>
Signed-off-by: Thomas Ackermann &lt;th.acker@arcor.de&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Documentation: avoid poor-man's small caps GIT</title>
<updated>2013-02-01T21:53:25Z</updated>
<author>
<name>Thomas Ackermann</name>
<email>th.acker@arcor.de</email>
</author>
<published>2013-01-21T19:16:20Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=48a8c26c625a4d3631c4f614bceb38933e741408'/>
<id>urn:sha1:48a8c26c625a4d3631c4f614bceb38933e741408</id>
<content type='text'>
In the earlier days, we used to spell the name of the system as GIT,
to simulate as if it were typeset with capital G and IT in small
caps.  Later we stopped doing so at around 1.6.5 days.

Let's stop doing so throughout the documentation.  The name to refer
to the whole system (and the concept it embodies) is "Git"; the
command end-users type is "git".  And document this in the coding
guideline.

Signed-off-by: Thomas Ackermann &lt;th.acker@arcor.de&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
</feed>
