Re: [PATCH v6 03/15] bugreport: add tool to generate debugging info

From: SZEDER Gábor <szeder.dev@gmail.com>
Date: Feb 7, 2020, 14:54 UTC
Message-ID: <20200207145409.GG2868@szeder.dev>
In-Reply-To: <20200206004108.261317-4-emilyshaffer@google.com>

On Wed, Feb 05, 2020 at 04:40:56PM -0800, Emily Shaffer wrote:

Show 24 quoted lines

> Teach Git how to prompt the user for a good bug report: reproduction
> steps, expected behavior, and actual behavior. Later, Git can learn how
> to collect some diagnostic information from the repository.
> 
> If users can send us a well-written bug report which contains diagnostic
> information we would otherwise need to ask the user for, we can reduce
> the number of question-and-answer round trips between the reporter and
> the Git contributor.
> 
> Users may also wish to send a report like this to their local "Git
> expert" if they have put their repository into a state they are confused
> by.
> 
> Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
> ---
>  .gitignore                      |  1 +
>  Documentation/git-bugreport.txt | 41 ++++++++++++++++
>  Makefile                        |  5 ++
>  bugreport.c                     | 85 +++++++++++++++++++++++++++++++++
>  t/t0091-bugreport.sh            | 49 +++++++++++++++++++
>  5 files changed, 181 insertions(+)
>  create mode 100644 Documentation/git-bugreport.txt
>  create mode 100644 bugreport.c
>  create mode 100755 t/t0091-bugreport.sh

Please add a corresponding entry to 'command-list.txt' as well. According to the comment at the beginning of that file, all, even external commands should be included there.