From: Christian Couder <christian.couder@gmail.com>
To: Siddharth Asthana <siddharthasthana31@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com, johncai86@gmail.com,
Johannes.Schindelin@gmx.de, avarab@gmail.com, me@ttaylorr.com
Subject: Re: [PATCH v6 2/2] cat-file: add mailmap support to --batch-check option
Date: Wed, 14 Dec 2022 15:04:17 +0100 [thread overview]
Message-ID: <CAP8UFD0_86GiwNXmCZzVfDJTE5C6KWz=8F9S4hVEA5Xi8XhgDw@mail.gmail.com> (raw)
In-Reply-To: <20221201155504.320461-3-siddharthasthana31@gmail.com>
On Thu, Dec 1, 2022 at 4:55 PM Siddharth Asthana
<siddharthasthana31@gmail.com> wrote:
> diff --git a/Documentation/git-cat-file.txt b/Documentation/git-cat-file.txt
> index f82d702d6b..81235c60a3 100644
> --- a/Documentation/git-cat-file.txt
> +++ b/Documentation/git-cat-file.txt
> @@ -91,26 +91,49 @@ OPTIONS
> --batch::
> --batch=<format>::
> Print object information and contents for each object provided
> - on stdin. May not be combined with any other options or arguments
> - except `--textconv` or `--filters`, in which case the input lines
Nit: here there were backticks around --textconv and --filters ...
> - also need to specify the path, separated by whitespace. See the
> - section `BATCH OUTPUT` below for details.
> + on stdin. May not be combined with any other options or arguments
> + except --textconv, --filters, or --use-mailmap.
... but here there are no backticks anymore.
It would be better if backticks were used.
> + +
> + * When used with `--textconv` or `--filters`, the input lines
Here and below backticks are used which is good.
> + must specify the path, separated by whitespace. See the section
> + `BATCH OUTPUT` below for details.
> + +
> + * When used with `--use-mailmap`, for commit and tag objects, the
> + contents part of the output shows the identities replaced using the
> + mailmap mechanism, while the information part of the output shows
> + the size of the object as if it actually recorded the replacement
> + identities.
>
> --batch-check::
> --batch-check=<format>::
> - Print object information for each object provided on stdin. May
> - not be combined with any other options or arguments except
> - `--textconv` or `--filters`, in which case the input lines also
> - need to specify the path, separated by whitespace. See the
> - section `BATCH OUTPUT` below for details.
> + Print object information for each object provided on stdin. May not be
> + combined with any other options or arguments except --textconv, --filters
> + or --use-mailmap.
Here backticks are also missing.
> + +
> + * When used with `--textconv` or `--filters`, the input lines must
> + specify the path, separated by whitespace. See the section
> + `BATCH OUTPUT` below for details.
> + +
> + * When used with `--use-mailmap`, for commit and tag objects, the
> + printed object information shows the size of the object as if the
> + identities recorded in it were replaced by the mailmap mechanism.
>
> --batch-command::
> --batch-command=<format>::
> Enter a command mode that reads commands and arguments from stdin. May
> - only be combined with `--buffer`, `--textconv` or `--filters`. In the
> - case of `--textconv` or `--filters`, the input lines also need to specify
> - the path, separated by whitespace. See the section `BATCH OUTPUT` below
> - for details.
> + only be combined with `--buffer`, `--textconv`, `--use-mailmap` or
> + `--filters`.
Here they are used which is good.
> + +
> + * When used with `--textconv` or `--filters`, the input lines must
> + specify the path, separated by whitespace. See the section
> + `BATCH OUTPUT` below for details.
> + +
> + * When used with `--use-mailmap`, for commit and tag objects, the
> + `contents` command shows the identities replaced using the
> + mailmap mechanism, while the `info` command shows the size
> + of the object as if it actually recorded the replacement
> + identities.
Thanks!
next prev parent reply other threads:[~2022-12-14 14:05 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 20:59 [PATCH 0/3] Add mailmap mechanism in --batch-check options Siddharth Asthana
2022-09-16 20:59 ` [PATCH 1/3] doc/cat-file: allow --use-mailmap for --batch options Siddharth Asthana
2022-09-16 22:02 ` Junio C Hamano
2022-09-16 20:59 ` [PATCH 2/3] cat-file: add mailmap support to -s option Siddharth Asthana
2022-09-16 22:22 ` Junio C Hamano
2022-09-16 20:59 ` [PATCH 3/3] cat-file: add mailmap support to --batch-check option Siddharth Asthana
2022-09-16 22:35 ` Junio C Hamano
2022-09-26 10:53 ` [PATCH v2 0/2] Add mailmap mechanism in cat-file options Siddharth Asthana
2022-09-26 10:53 ` [PATCH v2 1/2] cat-file: add mailmap support to -s option Siddharth Asthana
2022-09-26 13:16 ` Ævar Arnfjörð Bjarmason
2022-09-26 13:25 ` Ævar Arnfjörð Bjarmason
2022-09-26 10:53 ` [PATCH v2 2/2] cat-file: add mailmap support to --batch-check option Siddharth Asthana
2022-10-29 10:24 ` [PATCH v3 0/2] Add mailmap mechanism in cat-file options Siddharth Asthana
2022-10-29 10:24 ` [PATCH v3 1/2] cat-file: add mailmap support to -s option Siddharth Asthana
2022-10-31 11:49 ` Christian Couder
2022-10-29 10:24 ` [PATCH v3 2/2] cat-file: add mailmap support to --batch-check option Siddharth Asthana
2022-10-31 11:43 ` Christian Couder
2022-10-29 18:00 ` [PATCH v3 0/2] Add mailmap mechanism in cat-file options Taylor Blau
2022-11-13 21:28 ` [PATCH v4 0/3] " Siddharth Asthana
2022-11-13 21:28 ` [PATCH v4 1/3] cat-file: add mailmap support to -s option Siddharth Asthana
2022-11-13 21:28 ` [PATCH v4 2/3] cat-file: add mailmap support to --batch-check option Siddharth Asthana
2022-11-15 21:40 ` Taylor Blau
2022-11-13 21:28 ` [PATCH v4 3/3] doc/cat-file: allow --use-mailmap for --batch options Siddharth Asthana
2022-11-14 17:48 ` [PATCH v4 0/3] Add mailmap mechanism in cat-file options Christian Couder
2022-11-14 22:30 ` Taylor Blau
2022-11-20 7:42 ` Siddharth Asthana
2022-11-20 7:48 ` [PATCH v5 0/2] " Siddharth Asthana
2022-11-20 7:48 ` [PATCH v5 1/2] cat-file: add mailmap support to -s option Siddharth Asthana
2022-11-21 7:27 ` Junio C Hamano
2022-11-21 9:40 ` Christian Couder
2022-11-21 9:45 ` Junio C Hamano
2022-11-21 11:27 ` Ævar Arnfjörð Bjarmason
2022-11-20 7:48 ` [PATCH v5 2/2] cat-file: add mailmap support to --batch-check option Siddharth Asthana
2022-11-21 7:38 ` Junio C Hamano
2022-11-30 9:19 ` Junio C Hamano
2022-12-01 15:55 ` [PATCH v6 0/2] Add mailmap mechanism in cat-file options Siddharth Asthana
2022-12-01 15:55 ` [PATCH v6 1/2] cat-file: add mailmap support to -s option Siddharth Asthana
2022-12-01 15:55 ` [PATCH v6 2/2] cat-file: add mailmap support to --batch-check option Siddharth Asthana
2022-12-14 11:27 ` Ævar Arnfjörð Bjarmason
2022-12-14 14:04 ` Christian Couder [this message]
2022-12-20 6:01 ` [PATCH v7 0/2] Add mailmap mechanism in cat-file options Siddharth Asthana
2022-12-20 6:01 ` [PATCH v7 1/2] cat-file: add mailmap support to -s option Siddharth Asthana
2022-12-20 6:01 ` [PATCH v7 2/2] cat-file: add mailmap support to --batch-check option Siddharth Asthana
2022-12-20 13:02 ` [PATCH v7 0/2] Add mailmap mechanism in cat-file options Ævar Arnfjörð Bjarmason
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP8UFD0_86GiwNXmCZzVfDJTE5C6KWz=8F9S4hVEA5Xi8XhgDw@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johncai86@gmail.com \
--cc=me@ttaylorr.com \
--cc=siddharthasthana31@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).