From: Junio C Hamano <gitster@pobox.com>
To: Linus Arver <linusa@google.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 1/3] update-index doc: v4 is OK with JGit and libgit2
Date: Tue, 12 Sep 2023 10:14:13 -0700 [thread overview]
Message-ID: <xmqq7covpb4q.fsf@gitster.g> (raw)
In-Reply-To: <owlyfs3kkmzd.fsf@fine.c.googlers.com> (Linus Arver's message of "Mon, 11 Sep 2023 21:57:10 -0700")
Linus Arver <linusa@google.com> writes:
> Junio C Hamano <gitster@pobox.com> writes:
> ...
>> +Older editions of this manual page called it "relatively young", but
>
> Nit: s/editions/versions because typically "edition" means a version of
> physically published text (such as books).
This text belonging to the manual, that was exactly the reason why I
used that word, but ...
> Also I don't think we use the
> word "edition" anywhere else in our codebase.
... I think "version" is just fine. Will fix.
Thanks.
next prev parent reply other threads:[~2023-09-12 17:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 23:37 [PATCH v2 0/3] "update-index --show-index-version" Junio C Hamano
2023-08-18 23:37 ` [PATCH v2 1/3] update-index doc: v4 is OK with JGit and libgit2 Junio C Hamano
2023-09-12 4:57 ` Linus Arver
2023-09-12 17:14 ` Junio C Hamano [this message]
2023-08-18 23:37 ` [PATCH v2 2/3] update-index: add --show-index-version Junio C Hamano
2023-09-12 5:54 ` Linus Arver
2023-09-12 19:01 ` Junio C Hamano
2023-08-18 23:37 ` [PATCH v2 3/3] test-tool: retire "index-version" Junio C Hamano
2023-09-12 6:10 ` Linus Arver
2023-09-12 19:32 ` [PATCH v3 0/3] "update-index --show-index-version" Junio C Hamano
2023-09-12 19:32 ` [PATCH v3 1/3] update-index doc: v4 is OK with JGit and libgit2 Junio C Hamano
2023-09-12 19:32 ` [PATCH v3 2/3] update-index: add --show-index-version Junio C Hamano
2023-11-14 2:18 ` Teng Long
2023-11-14 2:55 ` Junio C Hamano
2023-09-12 19:32 ` [PATCH v3 3/3] test-tool: retire "index-version" Junio C Hamano
2023-09-14 6:19 ` [PATCH v3 0/3] "update-index --show-index-version" Linus Arver
2023-09-14 18:15 ` Junio C Hamano
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=xmqq7covpb4q.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=linusa@google.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.
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.