In the "Reporting Bugs" section of git(1), we refer to the mailing list, but we do not give any hint about where the archives might be found. Of course, any web search engine can be used to try to hunt down whether an issue is already known. But we can do better by mentioning the archive at public-inbox. Make sure to phrase this in a way that avoids raising the bar for reporting. public-inbox.org/git/ is usually our preferred archive, since it uses message ids in its permalinks. But it also has a search function right at the top of each page, and searching gives the most recent hits first. Searching for some keyword about a bug or regression should pretty easily reveal whether it has been recently reported. Helped-by: Junio C Hamano <gitster@xxxxxxxxx> Signed-off-by: Martin Ågren <martin.agren@xxxxxxxxx> --- Thanks Junio and Taylor for thoughts on this. I agree we do not want to scare anyone away. I hope this does the trick. Documentation/git.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Documentation/git.txt b/Documentation/git.txt index 74a9d7edb4..68393f3235 100644 --- a/Documentation/git.txt +++ b/Documentation/git.txt @@ -859,6 +859,9 @@ Reporting Bugs Report bugs to the Git mailing list <git@xxxxxxxxxxxxxxx> where the development and maintenance is primarily done. You do not have to be subscribed to the list to send a message there. +If you want to check to see if the issue has +been reported already, the list archive can be found at +<https://public-inbox.org/git/> and other places. Issues which are security relevant should be disclosed privately to the Git Security mailing list <git-security@xxxxxxxxxxxxxxxx>. -- 2.19.0.216.g2d3b1c576c
