[PATCH] git doc: direct bug reporters to mailing list archive (Re: [PATCH v2] git.txt: mention mailing list archive)
- From
Jonathan Nieder <jrnieder@gmail.com>
- Date
- Sep 28, 2018, 21:20 UTC
- Message-ID
- <20180928212049.GD193055@aiede.svl.corp.google.com>
- In-Reply-To
- <xmqq1s9def2p.fsf@gitster-ct.c.googlers.com>
Subject: git doc: direct bug reporters to mailing list archive
The mailing list archive can help a user encountering a bug to tell whether a recent regression has already been reported and whether a longstanding bug has already had some discussion to start their thinking.
Based-on-patch-by: Martin Ågren <martin.agren@gmail.com> Improved-by: Junio C Hamano <gitster@pobox.com> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> --- Junio C Hamano wrote:
>> Jonathan Nieder wrote:
>>> Hm. I think this encourages a behavior that I want to discourage: >>> assuming that if a bug has already been reported then there's nothing >>> more for the new user to add.
[...]
> Yup, in short I think any one of the above three is good enough. > Let's just pick one and move on. Unless somebody sends in an > improvement that can be applied readily, by default I'll just "git > am" the one Martin sent, as that is the easiest thing to do ;-).
I assume this is meant as a nudge, in which case nudge successful. ;-)
My experience is that bug reporters are very sensitive to hints the project gives about what kind of bugs they want to receive. I'd rather make use of that lesson now instead of waiting to relearn it in the wild. Here goes.
Thanks, both.
Documentation/git.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/git.txt b/Documentation/git.txt index 74a9d7edb4..8e6a92e8ba 100644 --- a/Documentation/git.txt +++ b/Documentation/git.txt @@ -858,7 +858,9 @@ Reporting Bugs Report bugs 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. +subscribed to the list to send a message there. See the list archive +at https://public-inbox.org/git for previous bug reports and other +discussions. Issues which are security relevant should be disclosed privately to the Git Security mailing list <git-security@googlegroups.com>.
-- 2.19.0.605.g01d371f741