On Thu, May 28, 2020 at 04:33:16PM -0700, Junio C Hamano wrote: > > Emily Shaffer <emilyshaffer@xxxxxxxxxx> 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)? Yes, I noticed it late. I have no idea how it happened - I imagine I leaned on my touchpad (middle mouse paste) while typing or otherwise mashed some keys in Vim. In other words, the tool was me :) Have fixed it locally, thanks for spying it. - Emily
