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

Re: Bug reporting method too hard to find

From
Jeff King <peff@peff.net>
Date
Oct 29, 2014, 20:17 UTC
Message-ID
<20141029201756.GB27413@peff.net>
In-Reply-To
<20141029115857.GB33348@bat.dot-bit.org>
On Wed, Oct 29, 2014 at 11:58:57AM +0000, Francis Irving wrote:
> I could not find out how to report a bug. In the end, a colleague
> had to tell me.

Thanks for your suggestions; they all seem like improvements. I just opened:

  https://github.com/git/git-scm.com/pull/462

which implements most of them. Unlike development of git itself, which happens on the mailing list, development of the website is centered around that GitHub repository; if you have further suggestions for the site, they'll probably get more attention by opening an issue there.

-Peff
Previous: Francis Irving
Message 2 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.