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

Re: When and how to to contact the Git developers (gist)

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Apr 13, 2015, 21:10 UTC
Message-ID
<20150413211002.GD5467@google.com>
In-Reply-To
<CAEcj5uW2Shh4QvtmenW2h6KXYUCoEe5bHYNv_HVFQgUit=cJ0w@mail.gmail.com>
Hi,
Thomas Ferris Nicolaisen wrote:
>              Perhaps someone here would prefer to use my gist when
> redirecting people with "user questions" away from this list, or
> inspire them to write better bug reports.

This won't come as a surprise given what I said at Git Merge: I'd rather we don't redirect people with user questions away from this list. The current volume has been pleasant and manageable.

I especially disagree with
	Generally speaking, Git has very few bugs, and if you're not
	sure what you are doing, it's probably a user-issue, and not
	an issue for the Git developers.

User issues are an issue for git developers. The hardest part of making git work well is getting it to match how humans work, not getting it to be technically correct or theoretically bug free.

So if I were writing it, I'd drop everything up to "If you believe you've found a bug in Git for Windows".

Another alternate forum to point people to is #git on freenode. It is reachable from https://webchat.freenode.net, so a person seeking quick help doesn't even have to set up an IRC client.

It might be nice to add a note to the "If you can find no existing discussions" paragraph: if there's been a previous discussion, it's fine to raise the subject again. A good practice is to link to and summarize the previous discussion so people can learn from what has happened before.

On the other hand inspiring people about how to tell stories better or write bug reports in a more useful way is always welcome.

Thanks, Jonathan

Previous: Thomas Ferris NicolaisenNext: Thomas Ferris Nicolaisen
Message 4 of 5 in “When and how to to contact the Git developers (gist)”
  1. Thomas Ferris NicolaisenApr 10, 2015
  2. Junio C HamanoApr 13, 2015
  3. Thomas Ferris NicolaisenApr 13, 2015
  4. Jonathan NiederApr 13, 2015
  5. Thomas Ferris NicolaisenApr 14, 2015

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.