Re: [PATCH 23/24] t5505,t5516: create .git/branches/ when needed

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 19, 2019, 16:30 UTC
Message-ID: <xmqq8ssuvvf4.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <xmqqd0i6vxwt.fsf@gitster-ct.c.googlers.com>

Junio C Hamano <gitster@pobox.com> writes:

Show 7 quoted lines

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
>> You probably forgot that I already proposed that, long time ago:
>> https://public-inbox.org/git/cover.1494509599.git.johannes.schindelin@gmx.de/
>
> No, I haven't.  It was actually meant as an invitation to you to
> help us come up with a reasonable deprecation path.

By the way, while the "deprecation plan" still has my attention ;-), there is another thing I've been wanting to see happen *without* burning me like the last time it was brought up [*1*], which is also hard to come up with a reasonable deprecation path.

A newer port like Git for Windows, where I suspect that most of the users are not even aware of the "git-foo" form, can probably get away by not shipping the libexec/git/git-foo without getting its users complaining (and as you repeatedly said, nobody on Windows write shell scripts, so lack of support for old scripts writtin in the days back when git-foo was a norm is perfectly fine there). But I am not sure about my tree where audiences are beyond Windows, and I certainly do not want to get burned again myself.

Somebody else volunteering to take both blame (and flame) and credit would be most welcomed ;-).

[Reference]

*1* https://public-inbox.org/git/7vr68b8q9p.fsf@gitster.siamese.dyndns.org/