From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Cc: Emily Shaffer <emilyshaffer@google.com>,
Junio C Hamano <gitster@pobox.com>,
Felipe Contreras <felipe.contreras@gmail.com>
Subject: [PATCH] bugreport: add quoted line prefixes
Date: Fri, 23 Jul 2021 12:59:50 -0500 [thread overview]
Message-ID: <20210723175950.64955-1-felipe.contreras@gmail.com> (raw)
With quoted line prefixes it's easier to distinguish what are the
standard questions, and what are the user responses.
Additionally it's easier for the reporter to visualize what has she
responded.
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
---
Lately I've seen a bunch of bug reports on the mailing list, but I find
it hard to parse the questions from the responses.
builtin/bugreport.c | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/builtin/bugreport.c b/builtin/bugreport.c
index 9915a5841d..10e55afe37 100644
--- a/builtin/bugreport.c
+++ b/builtin/bugreport.c
@@ -94,21 +94,21 @@ static const char * const bugreport_usage[] = {
static int get_bug_template(struct strbuf *template)
{
const char template_text[] = N_(
-"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"
-"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"
-"What did you expect to happen? (Expected behavior)\n"
+"> What did you expect to happen? (Expected behavior)\n"
"\n"
-"What happened instead? (Actual behavior)\n"
+"> What happened instead? (Actual behavior)\n"
"\n"
-"What's different between what you expected and what actually happened?\n"
+"> What's different between what you expected and what actually happened?\n"
"\n"
-"Anything else you want to add:\n"
+"> Anything else you want to add:\n"
"\n"
-"Please review the rest of the bug report below.\n"
-"You can delete any lines you don't wish to share.\n");
+"> Please review the rest of the bug report below.\n"
+"> You can delete any lines you don't wish to share.\n");
strbuf_addstr(template, _(template_text));
return 0;
--
2.32.0.40.gb9b36f9b52
reply other threads:[~2021-07-23 18:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210723175950.64955-1-felipe.contreras@gmail.com \
--to=felipe.contreras@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.