Re: [PATCH] bugreport: add tool to generate debugging info
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Aug 15, 2019, 20:07 UTC
- Message-ID
- <nycvar.QRO.7.76.6.1908152205390.46@tvgsbejvaqbjf.bet>
- In-Reply-To
- <e6d56d97-99c9-064a-71b5-2b7eb9b71e01@gmail.com>
Hi,
On Thu, 15 Aug 2019, Derrick Stolee wrote:
Show 11 quoted lines
> On 8/14/2019 10:34 PM, Emily Shaffer wrote: > > diff --git a/git-bugreport.sh b/git-bugreport.sh > > new file mode 100755 > > index 0000000000..2200703a51 > > --- /dev/null > > +++ b/git-bugreport.sh > > At first I was alarmed by "What? another shell script?" but this > command should prioritize flexibility and extensibility over speed. > Running multiple processes shouldn't be too taxing for what we are > trying to do here.
Git for Windows sometimes receives bug reports about Bash not being able to start (usually it is a DLL base address problem, related to the way Cygwin and MSYS2 emulate `fork()`).
In such a case, `git bugreport` would only be able to offer a reason for yet another bug report instead of adding useful metadata.
Something to keep in mind when deciding how to implement this command.
Ciao, Dscho