Re: [PATCH] bash-completion: Print a useful error when called in a non-bash shell
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:49:13
Subsystem:
documentation, the rest · Maintainers:
Jonathan Corbet, Linus Torvalds
Possibly related (same subject, not in this thread)
- 2016-06-15 · Re: [PATCH] bash-completion: Print a useful error when called in a non-bash shell · Johannes Sixt <hidden>
- 2016-06-15 · Re: [PATCH] bash-completion: Print a useful error when called in a non-bash shell · Junio C Hamano <hidden>
- 2016-06-15 · Re: [PATCH] bash-completion: Print a useful error when called in a non-bash shell · solsTiCe d'Hiver <hidden>
- 2016-06-15 · Re: [PATCH] bash-completion: Print a useful error when called in a non-bash shell · Andrew Sayers <hidden>
- 2016-06-15 · Re: [PATCH] bash-completion: Print a useful error when called in a non-bash shell · Ævar Arnfjörð Bjarmason <hidden>
Andrew Sayers [off-list ref] writes:
Would you be amenable in principle to creating something like `man git-bug`? A quick search doesn't turn up any documents specifically about bug fixing/reporting, and a man page was the first place I thought to look.
I'd be perfectly fine with something like this. People may want to add a sentence or two to give tips on how to make sure that they are actual bugs. Documentation/git.txt | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/Documentation/git.txt b/Documentation/git.txt
index 59f291d..3ba004f 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt@@ -727,6 +727,14 @@ The documentation for git suite was started by David Greaves <david@dgreaves.com>, and later enhanced greatly by the contributors on the git-list <git@vger.kernel.org>. +Reporting Bugs +-------------- + +If you found a bug, please send a bug report to the Git mailing list +<git@vger.kernel.org>, where the development and maintenance is primarily +done. You do not have to be subscribed to the list to send a message +there. + SEE ALSO -------- linkgit:gittutorial[7], linkgit:gittutorial-2[7],