git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "SZEDER Gábor" <szeder.dev@gmail.com>
Subject: Re: What's cooking in git.git (Sep 2020, #04; Wed, 16)
Date: Sun, 20 Sep 2020 19:02:55 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.2009201846040.5061@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqq363gqdzq.fsf@gitster.c.googlers.com>

Hi Junio,

On Thu, 17 Sep 2020, Junio C Hamano wrote:

> 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.

Thank you for the gentle reminder. I fixed up the branch locally (and had
to rebase it, to resolve merge conflicts with `jk/slimmed-down`) and will
send out v4 soon..

Ciao,
Dscho

      reply	other threads:[~2020-09-21 22:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17  3:47 What's cooking in git.git (Sep 2020, #04; Wed, 16) Junio C Hamano
2020-09-17 12:54 ` ds/maintenance-part-1 (was Re: What's cooking in git.git (Sep 2020, #04; Wed, 16)) Derrick Stolee
2020-09-17 16:36   ` Junio C Hamano
2020-09-17 17:37     ` Derrick Stolee
2020-09-17 19:52 ` What's cooking in git.git (Sep 2020, #04; Wed, 16) Junio C Hamano
2020-09-17 21:39 ` Junio C Hamano
2020-09-20 17:02   ` Johannes Schindelin [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=nycvar.QRO.7.76.6.2009201846040.5061@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=szeder.dev@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).