From: Junio C Hamano <gitster@pobox.com>
To: Andrew Sayers <andrew-git@pileofstuff.org>
Cc: Git Mailing List <git@vger.kernel.org>,
solsTiCe d'Hiver <solstice.dhiver@gmail.com>
Subject: Re: [PATCH] bash-completion: Print a useful error when called in a non-bash shell
Date: Thu, 29 Jul 2010 16:38:20 -0700 [thread overview]
Message-ID: <7vr5ilsvtf.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4C51F2C0.8090101@pileofstuff.org> (Andrew Sayers's message of "Thu\, 29 Jul 2010 22\:29\:36 +0100")
Andrew Sayers <andrew-git@pileofstuff.org> 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],
next prev parent reply other threads:[~2010-07-29 23:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 22:32 [PATCH] bash-completion: Print a useful error when called in a non-bash shell Andrew Sayers
2010-07-29 16:25 ` Junio C Hamano
2010-07-29 19:05 ` solsTiCe d'Hiver
2010-07-29 21:29 ` Andrew Sayers
2010-07-29 22:16 ` Ævar Arnfjörð Bjarmason
2010-07-29 23:38 ` Junio C Hamano [this message]
2010-07-30 6:02 ` Stephen Boyd
2010-08-06 21:31 ` Johannes Sixt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vr5ilsvtf.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=andrew-git@pileofstuff.org \
--cc=git@vger.kernel.org \
--cc=solstice.dhiver@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).