public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>
To: "Junio C Hamano" <gitster@pobox•com>
Cc: git@vger•kernel.org,
	"Kristoffer Haugsbakk" <code@khaugsbakk•name>,
	"Emily Shaffer" <nasamuffin@google•com>
Subject: Re: [PATCH v2] bugreport: use quoted line prefixes
Date: Sat, 23 Aug 2025 10:23:11 +0200	[thread overview]
Message-ID: <2289e675-47b0-4cd1-aeb2-53664597e0f7@app.fastmail.com> (raw)
In-Reply-To: <xmqq5xeosgm3.fsf@gitster.g>

On Fri, Aug 15, 2025, at 18:18, Junio C Hamano wrote:
> kristofferhaugsbakk@fastmail•com writes:
>
>> From: Kristoffer Haugsbakk <code@khaugsbakk•name>
>>
>> Quoted line prefixes make it easier to distinguish between the questions
>> and the answers, both for the reporter and for the readers.
>
> This may improve things a bit, but the #1 thing that made the
> reports most hard to read for me, while reading bugreport output
> posted here over time, is lack of a blank line between each question
> and its answer (and the tail end of an answer and the beginning of
> the next question).

I’ve added this in the [v3].

[v3]: <3d00cdbe8535fda8f9e72b5243090e6d953c133e.1755866791.git.code@khaugsbakk•name>

>> -"Thank you for filling out a Git bug report!\n"
>> -"Please answer the following questions to help us understand your issue.\n"
>> +"> Thank you for filling out a Git bug report!\n"
>> +"> Please answer the following questions to help us understand your issue.\n"
>>  "\n"
>
> I do not see a need to quote the above.  Nobody will write in this
> space between the above introductory text and the first question
> below.

I agree.  This has been changed as well in v3.

>
>> -"What did you do before the bug happened? (Steps to reproduce your issue)\n"
>> +"> What did you do before the bug happened? (Steps to reproduce your issue)\n"
>>  "\n"
> [snip]

  reply	other threads:[~2025-08-23  8:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23 17:59 [PATCH] bugreport: add quoted line prefixes Felipe Contreras
2025-08-15 11:10 ` [PATCH v2] bugreport: use " kristofferhaugsbakk
2025-08-15 16:18   ` Junio C Hamano
2025-08-23  8:23     ` Kristoffer Haugsbakk [this message]
2025-08-22 12:49   ` [PATCH v3] bugreport: use quoted line prefixes & more blank lines kristofferhaugsbakk

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=2289e675-47b0-4cd1-aeb2-53664597e0f7@app.fastmail.com \
    --to=kristofferhaugsbakk@fastmail$(echo .)com \
    --cc=code@khaugsbakk$(echo .)name \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitster@pobox$(echo .)com \
    --cc=nasamuffin@google$(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