From: Jeff King <peff@peff.net>
To: Emily Shaffer <emilyshaffer@google.com>
Cc: git@vger.kernel.org, Philippe Blain <levraiphilippeblain@gmail.com>
Subject: Re: [git-scm.com PATCH] community: advertise 'git-bugreport' tool
Date: Thu, 28 May 2020 23:37:40 -0400 [thread overview]
Message-ID: <20200529033740.GD1271617@coredump.intra.peff.net> (raw)
In-Reply-To: <20200528231608.59507-1-emilyshaffer@google.com>
On Thu, May 28, 2020 at 04:16:08PM -0700, Emily Shaffer wrote:
> Since this patch deals with some prominent information about how to
> contact the community, I figured it was worth passing through the list
> for feedback rather than just sending a PR to the website repo.
> Discussion prior to this patch here:
> https://github.com/git/git-scm.com/issues/1464
Thanks for doing that. I'd echo my sentiment in that issue that if
anybody from list community is interested in suggesting changes to the
Community page, we're happy to take patches. The bug-reporting advice
there has been slowly added over the years, and fresh eyes may produce
useful insights.
> diff --git a/app/views/community/index.html.erb b/app/views/community/index.html.erb
> index 6927e19..bfcb089 100644
> --- a/app/views/community/index.html.erb
> +++ b/app/views/community/index.html.erb
> @@ -36,10 +36,13 @@
>
> <p>
> Bugs in git can be reported directly to the mailing list (see above for
> - details). Note that you do not need to subscribe to the list to send
> - to it. You can help us out by attempting to reproduce the bug in the latest
> - released version of git, or if you're willing to build git from source, the
> - <a href="https://github.com/git/git/tree/next"><code>next</code> branch</a>.
> + details). Note that you do not need to subscribe to the list to send to it.
> + If you are using git 2.27.0 or later, you can run <code>git bugreport</code>,
Perhaps make this a link to /docs/git-bugreport? That's not active yet,
but will be when we release v2.27 (scheduled for Monday). We could hold
this patch until then.
Other than that, looks good to me, modulo the /break/ thing mentioned
elsewhere.
-Peff
prev parent reply other threads:[~2020-05-29 3:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 23:16 [git-scm.com PATCH] community: advertise 'git-bugreport' tool Emily Shaffer
2020-05-28 23:33 ` Junio C Hamano
2020-05-28 23:53 ` Emily Shaffer
2020-05-29 0:27 ` Jonathan Nieder
2020-05-29 3:24 ` Jeff King
2020-05-29 1:49 ` Philippe Blain
2020-05-29 3:33 ` Jeff King
2020-05-29 3:37 ` Jeff King [this message]
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=20200529033740.GD1271617@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=levraiphilippeblain@gmail.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 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 NNTP newsgroup(s).