Re: [PATCH v3 1/9] bugreport: add tool to generate debugging info

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Nov 20, 2019, 10:51 UTC
Message-ID: <nycvar.QRO.7.76.6.1911201150260.15956@tvgsbejvaqbjf.bet>
In-Reply-To: <xmqq4kyzfknc.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Wed, 20 Nov 2019, Junio C Hamano wrote:

Show 13 quoted lines

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > FWIW I disagree with the idea that a tiny built-in command like
> > `bugreport` would "bloat" the main `git` binary.
> >
> > In contrast, I think that stand-alone commands _do_ bloat. Look here:
>
> I probably should have clarified that "bloat" in the context of this
> discussion is not about on-disk space.  It is about resources needed
> to run "git status/diff/etc" that are everyday local commands that
> are expected to be lightweight, i.e. the same criteria applied when
> making the networking part (which the user expects to be coffee time)
> separate from them.

I guess I still do not understand.

Are you suggesting that `bugreport` would be unwelcome as a built-in? If so, I would really like to know why. Because I think it would make for a very fine built-in. I interact with users all the time, and a good tool to provide good information to accompany a bug report is definitely something that would improve the current situation.

Ciao, Dscho