Git development
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Bug with bash and OpenSSL usage on Windows
Date: Sat, 27 Jul 2024 21:20:09 +0000	[thread overview]
Message-ID: <ZqVkiaD6L_zdfTJV@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <xmqqttgasufx.fsf@gitster.g>

[-- Attachment #1: Type: text/plain, Size: 2004 bytes --]

On 2024-07-27 at 15:53:06, Junio C Hamano wrote:
> "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?

I think something like that would be valuable.  We of course want to
hear about useful bug reports, but there's nothing we can do in this
case and it would be very helpful both for us and the reporter if it
went to the right place at first (even if that were the case even just a
slightly higher percentage of the time).

It might be helpful to maybe add a note that the reporter should search
for a similar issue first before reporting it.  I feel like Dscho, as
well as the Debian and Ubuntu maintainers, will appreciate that, and I
know for Ubuntu at least the issue tracker actually keeps track of the
issues affecting the most people to help prioritize fixes.
-- 
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  parent reply	other threads:[~2024-07-27 21:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-26 19:40 Bug with bash and OpenSSL usage on Windows Tim Abdiukov
2024-07-26 19:48 ` Tim Abdiukov
2024-07-27 14:36 ` brian m. carlson
2024-07-27 15:53   ` Junio C Hamano
2024-07-27 15:58     ` Junio C Hamano
2024-07-27 16:05     ` Eric Sunshine
2024-07-27 21:20     ` brian m. carlson [this message]
2024-07-27 22:01     ` Jeff King
2024-08-13 13:06 ` Johannes Schindelin

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=ZqVkiaD6L_zdfTJV@tapette.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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