From: Junio C Hamano <gitster@pobox•com>
To: Emily Shaffer <emilyshaffer@google•com>
Cc: git@vger•kernel.org, Jeff King <peff@peff•net>,
Philippe Blain <levraiphilippeblain@gmail•com>
Subject: Re: [git-scm.com PATCH] community: advertise 'git-bugreport' tool
Date: Thu, 28 May 2020 16:33:16 -0700 [thread overview]
Message-ID: <xmqqftbj1vpf.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200528231608.59507-1-emilyshaffer@google.com> (Emily Shaffer's message of "Thu, 28 May 2020 16:16:08 -0700")
Emily Shaffer <emilyshaffer@google•com> writes:
> <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>,
> + which generates a template to guide you through writing a useful bug report
> + and gathers some diagnostic information about your environment. 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:/break/github.com/git/git/tree/next"><code>next</code> branch</a>.
It took me a bit more then necessary to spot this due to rewrapping
of the string, but I do not think you meant "https:/break/" there.
Care to share how it happened (what tool has the tendency to
introduce this particular breakage)?
Thanks.
next prev parent reply other threads:[~2020-05-28 23:39 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 [this message]
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
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=xmqqftbj1vpf.fsf@gitster.c.googlers.com \
--to=gitster@pobox$(echo .)com \
--cc=emilyshaffer@google$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=levraiphilippeblain@gmail$(echo .)com \
--cc=peff@peff$(echo .)net \
/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