Re: What's cooking in git.git (Sep 2020, #04; Wed, 16)

> Junio C Hamano <gitster@pobox.com> writes:
>
> > * js/no-builtins-on-disk-option (2020-08-24) 3 commits
> >  - ci: stop linking built-ins to the dashed versions
> >  - install: optionally skip linking/copying the built-ins
> >  - msvc: copy the correct `.pdb` files in the Makefile target `install`
> >
> >  The installation procedure learned to optionally omit "git-foo"
> >  executable files for each 'foo' built-in subcommand, which are only
> >  required by old timers that still rely on the age old promise that
> >  prepending "git --exec-path" output to PATH early in their script
> >  will keep the "git-foo" calls they wrote working.
> >
> >  The old attempt to remove these executables from the disk failed in
> >  the 1.6 era; it may be worth attempting again, but I think it is
> >  worth to keep this topic separate from such a policy change to help
> >  it graduate early.
> >
> >  Expecting a reroll to update log message for the last one.
> >  as it confused at least two reviewers.
> >  cf. <xmqqwo1baop3.fsf@gitster.c.googlers.com>
> >  cf. <20200903104537.GA27325@szeder.dev>
>
> I think this is more or less good modulo the way the last bit is
> explained.  No rush, but just trying to make sure it will not stay
> stalled forever.