From: Junio C Hamano <gitster@pobox.com>
To: Emily Shaffer <emilyshaffer@google.com>
Cc: git@vger.kernel.org, Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH] Documentation: fix default directory of git bugreport -o
Date: Tue, 07 Sep 2021 14:09:46 -0700 [thread overview]
Message-ID: <xmqqa6ko9jol.fsf@gitster.g> (raw)
In-Reply-To: <20210903115933.622847-1-bagasdotme@gmail.com> (Bagas Sanjaya's message of "Fri, 3 Sep 2021 18:59:34 +0700")
Bagas Sanjaya <bagasdotme@gmail.com> writes:
> git bugreport writes bug report to the current directory by default,
> instead of repository root.
>
> Fix the documentation.
>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> Documentation/git-bugreport.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Emily, ack? It seems that after we cdup to the top, we adjust
either the value of -o or "" with the prefix to come up with the
output location, so the default seems to be "the current" as the
updated documentation says.
> diff --git a/Documentation/git-bugreport.txt b/Documentation/git-bugreport.txt
> index 66e88c2e31..d8817bf3ce 100644
> --- a/Documentation/git-bugreport.txt
> +++ b/Documentation/git-bugreport.txt
> @@ -40,8 +40,8 @@ OPTIONS
> -------
> -o <path>::
> --output-directory <path>::
> - Place the resulting bug report file in `<path>` instead of the root of
> - the Git repository.
> + Place the resulting bug report file in `<path>` instead of the current
> + directory.
>
> -s <format>::
> --suffix <format>::
>
> base-commit: 6c40894d2466d4e7fddc047a05116aa9d14712ee
prev parent reply other threads:[~2021-09-07 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 11:59 [PATCH] Documentation: fix default directory of git bugreport -o Bagas Sanjaya
2021-09-04 2:12 ` bugreport papercuts Carlo Marcelo Arenas Belón
2021-09-04 2:12 ` [PATCH 1/2] bugreport: avoid duplicating options in usage() Carlo Marcelo Arenas Belón
2021-09-07 21:39 ` Junio C Hamano
2021-09-04 2:12 ` [PATCH 2/2] bugreport: slightly better memory management Carlo Marcelo Arenas Belón
2021-09-07 21:56 ` Junio C Hamano
2021-09-04 6:01 ` bugreport papercuts Bagas Sanjaya
2021-09-07 21:09 ` Junio C Hamano [this message]
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=xmqqa6ko9jol.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=bagasdotme@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.