From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, scottworley@scottworley.com
Cc: git@vger.kernel.org, "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: Re: [PATCH] doc: update advice about other implementations' v4 index support
Date: Fri, 9 Apr 2021 21:12:59 -0400 [thread overview]
Message-ID: <6be901d0-1b7d-d4ef-388e-e7b2e4edbc7f@gmail.com> (raw)
In-Reply-To: <xmqq1rbjm617.fsf@gitster.g>
On 4/9/2021 6:45 PM, Junio C Hamano wrote:
> scottworley@scottworley.com writes:
>
>> From: Scott Worley <scottworley@scottworley.com>
>>
>> Signed-off-by: Scott Worley <scottworley@scottworley.com>
>> ---
>> Documentation/git-update-index.txt | 7 ++++---
>> 1 file changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/git-update-index.txt b/Documentation/git-update-index.txt
>> index 2853f168d9..e8eca5dadf 100644
>> --- a/Documentation/git-update-index.txt
>> +++ b/Documentation/git-update-index.txt
>> @@ -166,9 +166,10 @@ you will need to handle the situation manually.
>> +
>> Version 4 performs a simple pathname compression that reduces index
>> size by 30%-50% on large repositories, which results in faster load
>> -time. Version 4 is relatively young (first released in 1.8.0 in
>> -October 2012). Other Git implementations such as JGit and libgit2
>> -may not support it yet.
>> +time. Version 4 is relatively young (first released in git 1.8.0 in
>> +October 2012, supported in libgit2 0.24.4 from December 2016, go-git
>> +4.0.0 from January 2018, and jgit 5.9.0 from September 2020). Other
>> +Git implementations such as Dulwich may not support it yet.
>
> Thanks for these dates. Time flies---I didn't realize it has been
> almost 9 years---the feature was merged in May 2012, in v1.7.11
> (yes, I am hinting that the original lists a wrong date and we
> should correct it while at it).
>
> I wonder if we should lose "relatively young" from the description
> here, though.
I was thinking the same thing. It has had extensions added such as
the End-of-index extension, but even that is approaching three years
ago.
Thanks,
-Stolee
prev parent reply other threads:[~2021-04-10 1:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 20:22 [PATCH] doc: update advice about other implementations' v4 index support scottworley
2021-04-09 22:45 ` Junio C Hamano
2021-04-10 1:12 ` Derrick Stolee [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=6be901d0-1b7d-d4ef-388e-e7b2e4edbc7f@gmail.com \
--to=stolee@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=scottworley@scottworley.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 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 NNTP newsgroup(s).