Protocol v2 in v2.27 (Re: Re* [ANNOUNCE] Git v2.27.0-rc1)

2020-05-20 Thread Jonathan Nieder
(other lists -> bcc) Junio C Hamano wrote: > Jeff King writes: >> Is it worth mentioning here the reversion of v2 as the default protocol? >> >> It does end up (along with the actual code fix) in the "fixes from >> v2.26" section: >> >>> * Those fetching over protocol v2 from linux-next and

Re: Re* [ANNOUNCE] Git v2.27.0-rc1

2020-05-20 Thread Jeff King
On Wed, May 20, 2020 at 01:31:30PM -0700, Junio C Hamano wrote: > The promotion in Git 2.26 was buried in the "performance & > implementation details" section and not in the backward > compatibility section, so it feels a bit funny to highlight the > reversion. In any case, here is what I

Re: [ANNOUNCE] Git v2.27.0-rc1

2020-05-20 Thread Son Luong Ngoc
Hi folks, > Shourya Shukla (4): > submodule--helper.c: Rename 'cb_foreach' to 'foreach_cb' > gitfaq: files in .gitignore are tracked > gitfaq: fetching and pulling a repository > submodule: port subcommand 'set-url' from shell to C Could you please review the minor fix in

Re* [ANNOUNCE] Git v2.27.0-rc1

2020-05-20 Thread Junio C Hamano
Jeff King writes: > On Wed, May 20, 2020 at 12:17:11PM -0700, Junio C Hamano wrote: > >> Git 2.27 Release Notes (draft) >> == >> >> Updates since v2.26 >> --- >> >> Backward compatibility notes > > Is it worth mentioning here the reversion of v2 as

Re: [ANNOUNCE] Git v2.27.0-rc1

2020-05-20 Thread Junio C Hamano
Jeff King writes: > On Wed, May 20, 2020 at 12:17:11PM -0700, Junio C Hamano wrote: > >> Git 2.27 Release Notes (draft) >> == >> >> Updates since v2.26 >> --- >> >> Backward compatibility notes > > Is it worth mentioning here the reversion of v2 as

Re: [ANNOUNCE] Git v2.27.0-rc1

2020-05-20 Thread Jeff King
On Wed, May 20, 2020 at 12:17:11PM -0700, Junio C Hamano wrote: > Git 2.27 Release Notes (draft) > == > > Updates since v2.26 > --- > > Backward compatibility notes Is it worth mentioning here the reversion of v2 as the default protocol? It does end