From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: "Rubén Justo" <rjusto@gmail.com>,
"Git List" <git@vger.kernel.org>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Emily Shaffer" <nasamuffin@google.com>
Subject: Re: [PATCH 0/2] improve bugreports
Date: Mon, 01 Apr 2024 02:29:30 -0700 [thread overview]
Message-ID: <xmqq5xx1e8hx.fsf@gitster.g> (raw)
In-Reply-To: <CAPig+cRFqddMqTxCENnknv3Agcq3_bxGmB1sQTmJNb=xNYg1aw@mail.gmail.com> (Eric Sunshine's message of "Sun, 31 Mar 2024 23:09:02 -0400")
Eric Sunshine <sunshine@sunshineco.com> writes:
> redundancy. In particular, of the three questions:
>
> What did you expect to happen?
> What happened instead?
> What's different between what you expected
> and what actually happened?
>
> the final one seems to repeat what the first two ask, and it is common
> when answering the third question for people to simply repeat what was
> said in response to an earlier question.
The third one may need to be rephrased, but I think it should still
be there. The intent is to make the reporter realize how unhelpful
their answers are when they answer the first two questions with
- I expected it to work correctly
- It did not work correctly
They hopefully would realize that "work correctly" needs to be
elaborated in order to answer the third question in a useful way.
If the first two questions have been answered in a usable way, the
third one is often redundant.
next prev parent reply other threads:[~2024-04-01 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 17:32 [PATCH 0/2] improve bugreports Rubén Justo
2024-03-23 17:36 ` [PATCH 1/2] bugreport: add a new line between questions Rubén Justo
2024-03-23 17:36 ` [PATCH 2/2] bugreport: add a mark to each proposed questions Rubén Justo
2024-04-01 19:30 ` Kristoffer Haugsbakk
2024-04-01 19:33 ` Rubén Justo
2024-03-31 7:04 ` [PATCH 0/2] improve bugreports Rubén Justo
2024-04-01 3:09 ` Eric Sunshine
2024-04-01 9:29 ` Junio C Hamano [this message]
2024-04-01 19:27 ` Rubén Justo
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=xmqq5xx1e8hx.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=nasamuffin@google.com \
--cc=rjusto@gmail.com \
--cc=sunshine@sunshineco.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.