From: Bagas Sanjaya <bagasdotme@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Emily Shaffer <emilyshaffer@google.com>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH] bugreport: Add hint to answer questionnaire in English
Date: Fri, 3 Sep 2021 18:58:24 +0700 [thread overview]
Message-ID: <20210903115823.622715-1-bagasdotme@gmail.com> (raw)
Depending on system locale, git bugreport may launch the localized
bug report questionnaire (and thus users respond it in their native
language). However, many Git support forums (including
git@vger.kernel.org) expects bug reports written in English.
Add a hint that answering the questionnaire in English will increase
chances for bug reports to be responded.
Fixes: 238b439d69 (bugreport: add tool to generate debugging info,
2020-04-16)
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
In [1], Junio suggests to add hint for filling in bug report answers
in English. That stems from my responses to Krzysztof Żelechowski's bug
report [2], which advise him to re-submit the report in English.
[1]: https://lore.kernel.org/git/xmqqeeaiodxc.fsf@gitster.g/
[2]:
https://lore.kernel.org/git/22496693-cf63-a278-c85e-d9e4376e2a59@gmail.com/
builtin/bugreport.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/builtin/bugreport.c b/builtin/bugreport.c
index 9915a5841d..56ccd0fc41 100644
--- a/builtin/bugreport.c
+++ b/builtin/bugreport.c
@@ -96,6 +96,7 @@ 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"
+"Answering in English will give a better chance for your issue to be responded.\n"
"\n"
"What did you do before the bug happened? (Steps to reproduce your issue)\n"
"\n"
base-commit: 6c40894d2466d4e7fddc047a05116aa9d14712ee
--
2.25.1
reply other threads:[~2021-09-03 11:59 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210903115823.622715-1-bagasdotme@gmail.com \
--to=bagasdotme@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).