Re: [PATCH v3 0/2] Add reftable by default as a breaking change
- From
Karthik Nayak <karthik.188@gmail.com>
- Date
- Jul 4, 2025, 13:14 UTC
- Message-ID
- <CAOLa=ZS31zV==wu6YXG-9m=hUW_8gTkXbWCBJbCuS46+07HeFQ@mail.gmail.com>
- In-Reply-To
- <20250704-pks-reftable-default-backend-v3-0-a1eb63e8442a@pks.im>
Patrick Steinhardt <ps@pks.im> writes:
Show 30 quoted lines
> Hi, > > the recent thread at [1] motivated me to hack together this tiny patch > series that paves our path towards making the reftable backend the > default backend. It does two things: > > - It announces the breaking change for Git 3.0. > > - It makes it the default now already when "feature.experimental" is > enabled. > > The first item is subject to ecosystem support, most notably in > libraries like Gitoxide, libgit2 and JGit. The second item is intended > to extend the user base to power users so that we get more test exposure > out in the wild before we make it the default in Git 3.0. > > Changes in v2: > - Improve the breaking changes announcement a bit based on feedback. > - Introduce a `REF_STORAGE_FORMAT_DEFAULT` define. > - Print the default ref format as part of `git version --build-options`. > - Link to v1: https://lore.kernel.org/r/20250702-pks-reftable-default-backend-v1-0-84dbaddafb50@pks.im > > Changes in v3: > - Small tweaks to the commit messages. > - Mention better data compression as another benefit. > - Link to v2: https://lore.kernel.org/r/20250703-pks-reftable-default-backend-v2-0-5a27e72a8c5e@pks.im > > Thanks! > > Patrick
The changes in this version look good and as expected. This looks good to me.
Thanks
[snip]