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
