Re: Bug with bash and OpenSSL usage on Windows

> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
> 
> > The Git project doesn't ship OpenSSL, or, for that matter, any binaries
> > at all.  All we ship is source versions of Git which various
> > distributors compile, sometimes with other binaries.
> >
> > It looks like you're probably using Git for Windows, which _does_ ship
> > OpenSSL, and so you probably want to contact them using their issue
> > tracker[0] once you've verified that it hasn't already been reported.
> >
> > [0] https://github.com/git-for-windows/git
> 
> Thanks for giving a response like the above, tirelessly every time
> something similar pops out.
> 
> I've been wondering if we can somehow reduce the occurrence of such
> an issue in the first place.  Elaborating a bit more in the
> "Reporting bugs" section of the documentation landing page is
> probably the 0-th step, and if people agree that it is going in the
> right direction, perhaps we would extend it to include something
> similar to the top of the "git bugreport" template, by futzing with
> the implementation of builtin/bugreport.c:get_bug_template(), and we
> can even encourage customizing it by distribution.
> 
> Comments?