All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Thomas Ferris Nicolaisen <tfnico@gmail.com>
Cc: Git <git@vger.kernel.org>,
	Konstantin Khomoutov <flatworm@users.sourceforge.net>
Subject: Re: When and how to to contact the Git developers (gist)
Date: Mon, 13 Apr 2015 14:10:02 -0700	[thread overview]
Message-ID: <20150413211002.GD5467@google.com> (raw)
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

  parent reply	other threads:[~2015-04-13 21:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 13:40 When and how to to contact the Git developers (gist) Thomas Ferris Nicolaisen
2015-04-13  6:01 ` Junio C Hamano
2015-04-13  9:34   ` Thomas Ferris Nicolaisen
2015-04-13 21:10 ` Jonathan Nieder [this message]
2015-04-14 11:38   ` Thomas Ferris Nicolaisen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150413211002.GD5467@google.com \
    --to=jrnieder@gmail.com \
    --cc=flatworm@users.sourceforge.net \
    --cc=git@vger.kernel.org \
    --cc=tfnico@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.