<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/Documentation/git-bugreport.txt, branch v2.45.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.45.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.45.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2024-03-16T16:31:42Z</updated>
<entry>
<title>bugreport.c: fix a crash in `git bugreport` with `--no-suffix` option</title>
<updated>2024-03-16T16:31:42Z</updated>
<author>
<name>Jiamu Sun</name>
<email>barroit@linux.com</email>
</author>
<published>2024-03-14T04:00:16Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=b3b57c69dad91382ccc36ebf5d668454607dd568'/>
<id>urn:sha1:b3b57c69dad91382ccc36ebf5d668454607dd568</id>
<content type='text'>
`git bugreport` does not complain when `--no-suffix` is given, but
it leads to a segmentation fault as the it is not prepared to see a
NULL assigned to the option_suffix variable.

Signed-off-by: Jiamu Sun &lt;barroit@linux.com&gt;
Acked-by: Taylor Blau &lt;me@ttaylorr.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>doc: enforce dashes in placeholders</title>
<updated>2023-12-26T19:06:55Z</updated>
<author>
<name>Jean-Noël Avila</name>
<email>jn.avila@free.fr</email>
</author>
<published>2023-12-25T21:21:26Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=2162f9f6f86df4f49c3a716b5beb3952104ea8b8'/>
<id>urn:sha1:2162f9f6f86df4f49c3a716b5beb3952104ea8b8</id>
<content type='text'>
The CodingGuidelines documents stipulates that multi-word placeholders
are to be separated by dashes, not underscores nor spaces.

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>documentation: wording improvements</title>
<updated>2023-10-09T19:04:21Z</updated>
<author>
<name>Elijah Newren</name>
<email>newren@gmail.com</email>
</author>
<published>2023-10-08T06:45:03Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=cf6cac20059123d6ec3f867bb3692df62db52cf9'/>
<id>urn:sha1:cf6cac20059123d6ec3f867bb3692df62db52cf9</id>
<content type='text'>
Diff best viewed with --color-diff.

Signed-off-by: Elijah Newren &lt;newren@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>builtin/bugreport.c: create '--diagnose' option</title>
<updated>2022-08-12T20:20:02Z</updated>
<author>
<name>Victoria Dye</name>
<email>vdye@github.com</email>
</author>
<published>2022-08-12T20:10:17Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=aac0e8ffeeed57cae2a047fd442f2125cbfc8e39'/>
<id>urn:sha1:aac0e8ffeeed57cae2a047fd442f2125cbfc8e39</id>
<content type='text'>
Create a '--diagnose' option for 'git bugreport' to collect additional
information about the repository and write it to a zipped archive.

The '--diagnose' option behaves effectively as an alias for simultaneously
running 'git bugreport' and 'git diagnose'. In the documentation, users are
explicitly recommended to attach the diagnostics alongside a bug report to
provide additional context to readers, ideally reducing some back-and-forth
between reporters and those debugging the issue.

Note that '--diagnose' may take an optional string arg (either 'stats' or
'all'). If specified without the arg, the behavior corresponds to running
'git diagnose' without '--mode'. As with 'git diagnose', this default is
intended to help reduce unintentional leaking of sensitive information).
Users can also explicitly specify '--diagnose=(stats|all)' to generate the
respective archive created by 'git diagnose --mode=(stats|all)'.

Suggested-by: Ævar Arnfjörð Bjarmason &lt;avarab@gmail.com&gt;
Helped-by: Derrick Stolee &lt;derrickstolee@github.com&gt;
Signed-off-by: Victoria Dye &lt;vdye@github.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Documentation: fix default directory of git bugreport -o</title>
<updated>2021-09-07T21:25:13Z</updated>
<author>
<name>Bagas Sanjaya</name>
<email>bagasdotme@gmail.com</email>
</author>
<published>2021-09-03T11:59:34Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=ca0cc98e03e870f9b82b31f00b5c6ae422528e46'/>
<id>urn:sha1:ca0cc98e03e870f9b82b31f00b5c6ae422528e46</id>
<content type='text'>
git bugreport writes bug report to the current directory by default,
instead of repository root.

Fix the documentation.

Signed-off-by: Bagas Sanjaya &lt;bagasdotme@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'es/bugreport-shell'</title>
<updated>2020-06-09T01:06:28Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2020-06-09T01:06:28Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=ce095ecfe49791508860fc180bf67924d62503ba'/>
<id>urn:sha1:ce095ecfe49791508860fc180bf67924d62503ba</id>
<content type='text'>
"git bugreport" learns to report what shell is in use.

* es/bugreport-shell:
  bugreport: include user interactive shell
  help: add shell-path to --build-options
</content>
</entry>
<entry>
<title>Merge branch 'es/bugreport'</title>
<updated>2020-05-20T15:33:30Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2020-05-20T15:33:29Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=22954ba04d88d0962cf12657bd9eddf8b8d22f78'/>
<id>urn:sha1:22954ba04d88d0962cf12657bd9eddf8b8d22f78</id>
<content type='text'>
Doc fix.

* es/bugreport:
  git-bugreport.txt: adjust reference to strftime(3)
</content>
</entry>
<entry>
<title>git-bugreport.txt: adjust reference to strftime(3)</title>
<updated>2020-05-18T19:54:53Z</updated>
<author>
<name>Todd Zullinger</name>
<email>tmz@pobox.com</email>
</author>
<published>2020-05-18T19:37:36Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=01b62aaf11a0cbaa1ddce8a9e2b9940985a103af'/>
<id>urn:sha1:01b62aaf11a0cbaa1ddce8a9e2b9940985a103af</id>
<content type='text'>
The strftime(3) man page is outside of the Git suite.  Refererence it as
we do other external man pages and avoid creating a broken link when
generating the HTML documentation.

Signed-off-by: Todd Zullinger &lt;tmz@pobox.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>bugreport: include user interactive shell</title>
<updated>2020-05-13T05:02:20Z</updated>
<author>
<name>Emily Shaffer</name>
<email>emilyshaffer@google.com</email>
</author>
<published>2020-05-12T23:42:13Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=4a4804edf4d5f96407fc46eda802a3b29d991e33'/>
<id>urn:sha1:4a4804edf4d5f96407fc46eda802a3b29d991e33</id>
<content type='text'>
It's possible a user may complain about the way that Git interacts with
their interactive shell, e.g. autocompletion or shell prompt. In that
case, it's useful for us to know which shell they're using
interactively.

Signed-off-by: Emily Shaffer &lt;emilyshaffer@google.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>bugreport: collect list of populated hooks</title>
<updated>2020-05-08T01:25:04Z</updated>
<author>
<name>Emily Shaffer</name>
<email>emilyshaffer@google.com</email>
</author>
<published>2020-05-08T00:53:57Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=788a776069bffcbb7d0dd9b70d521826f97285b7'/>
<id>urn:sha1:788a776069bffcbb7d0dd9b70d521826f97285b7</id>
<content type='text'>
Occasionally a failure a user is seeing may be related to a specific
hook which is being run, perhaps without the user realizing. While the
contents of hooks can be sensitive - containing user data or process
information specific to the user's organization - simply knowing that a
hook is being run at a certain stage can help us to understand whether
something is going wrong.

Without a definitive list of hook names within the code, we compile our
own list from the documentation. This is likely prone to bitrot, but
designing a single source of truth for acceptable hooks is too much
overhead for this small change to the bugreport tool.

Signed-off-by: Emily Shaffer &lt;emilyshaffer@google.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
</feed>
