git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Bug reporting method too hard to find

From
FIFrancis Irving <francis@scraperwiki.com>
Date
Oct 29, 2014, 11:58 UTC
Message-ID
<20141029115857.GB33348@bat.dot-bit.org>

I could not find out how to report a bug. In the end, a colleague had to tell me.

Some suggested improvements:
1) Explicitly mention the word "bug" on the home page, or have
a page which Google will find called "Reporting bugs".
2) I did eventually get to the Community page:
http://git-scm.com/community

Alas, when I scanned the headline "Mailing List" I ignored that whole section because I didn't want to join a mailing list - I just wanted to report a bug.

I'd call it maybe "Mailing List and Bug Reporting". Or have a separate bugs section below called "Bug Reporting" which refers to the mailing list.

3) I definitely wasn't going to subscribe to a mailing list to report
a bug (no idea why - I'm just reporting my instinct which lots of
people likely have). 
I am only doing so because I saw that I don't have to subscribe.

I'm not sure how to make it clearer, but it needs to be as it is highly unintuitive. These days, you have to join most email lists to post to them.

This all matters, because Git is likely losing lots of basic bugs, particularly ones to do with usability for beginner users.

Thanks for a great tool!
Francis
Next: Jeff King
Message 1 of 2 in “Bug reporting method too hard to find”
  1. Francis IrvingOct 29, 2014
  2. Jeff KingOct 29, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.