From: Junio C Hamano <gitster@pobox•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: Sun, 12 Apr 2015 23:01:32 -0700 [thread overview]
Message-ID: <xmqqbnis4ldv.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAEcj5uW2Shh4QvtmenW2h6KXYUCoEe5bHYNv_HVFQgUit=cJ0w@mail.gmail.com> (Thomas Ferris Nicolaisen's message of "Fri, 10 Apr 2015 15:40:17 +0200")
Thomas Ferris Nicolaisen <tfnico@gmail•com> writes:
> At the Dev Summit, I mentioned this gist I've got lined up for
> whenever someone should consider sending an email to this list:
>
> https://gist.github.com/tfnico/4441562
>
> It's a handy link to share in some encounters, exemplified by Konstantin here:
>
> https://groups.google.com/d/msg/git-users/Md72iVvPHqw/Zi3yFIRrR2AJ
>
> I see that Peff already improved the git-scm.com/community late last
> year to cover some of the same points, but it is weighed a bit
> differently. 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.
As to "better bug reports", I often find people pointing others to
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
Even in a better report that gives specific precondition, input,
environment and output, sometimes I see one thing that is crucial
missing: what the user expected to see and how the output is
different from that expectation. Such a "bug report" may report the
designed behaviour, leaving the developers to scratch their heads,
"yeah, thanks for a detailed write-up, we can reproduce it exactly,
and everything is working as expected---how did you expect it to
work in what different way and why?".
next prev parent reply other threads:[~2015-04-13 6:01 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 [this message]
2015-04-13 9:34 ` Thomas Ferris Nicolaisen
2015-04-13 21:10 ` Jonathan Nieder
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=xmqqbnis4ldv.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=flatworm@users$(echo .)sourceforge.net \
--cc=git@vger$(echo .)kernel.org \
--cc=tfnico@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox