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> Improved-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jonathan Nieder committed
Sep 28, 2018 at 14:20 UTC
c56170a0c48c2a1068ff3b894e7a00658ab037f8
1 file changed
+3
-1
Documentation/git.txt
+3
-1
@@ -858,7 +858,9 @@ Reporting Bugs
858
859
Report bugs to the Git mailing list <git@vger.kernel.org> where the
860
development and maintenance is primarily done. You do not have to be
861
-subscribed to the list to send a message there.
861
+subscribed to the list to send a message there. See the list archive
862
+at https://public-inbox.org/git for previous bug reports and other
863
+discussions.
864
865
Issues which are security relevant should be disclosed privately to
866
the Git Security mailing list <git-security@googlegroups.com>.