Re: es/pathspec-f-f-grep, was Re: am/pathspec-f-f-checkout

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 6, 2019, 16:27 UTC
Message-ID: <xmqqeexhxvv3.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <nycvar.QRO.7.76.6.1912061622220.31080@tvgsbejvaqbjf.bet>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> Oops, I was talking about `es/pathspec-f-f-grep`, not about
> `am/pathspec-f-f-checkout`, sorry for the mixup.

Thanks. Yup, these uninitialized variables give a sign of carelessness. Will put on hold.

Show 27 quoted lines

> On Fri, 6 Dec 2019, Johannes Schindelin wrote:
>
>> Hi Junio & Emily,
>>
>> On Thu, 5 Dec 2019, Junio C Hamano wrote:
>>
>> > * am/pathspec-f-f-checkout (2019-12-04) 7 commits
>> >  - checkout, restore: support the --pathspec-from-file option
>> >  - doc: restore: synchronize <pathspec> description
>> >  - doc: checkout: synchronize <pathspec> description
>> >  - doc: checkout: fix broken text reference
>> >  - doc: checkout: remove duplicate synopsis
>> >  - add: support the --pathspec-from-file option
>> >  - cmd_add: prepare for next patch
>> >  (this branch uses am/pathspec-from-file; is tangled with es/pathspec-f-f-grep.)
>> >
>> >  A few more commands learned the "--pathspec-from-file" command line
>> >  option.
>> >
>> >  Will merge to 'next'.
>>
>> Gábor noticed that this breaks Travis, and I provided a patch that
>> initializes those new variables. Please squash that in before merging to
>> `next`.
>>
>> Thanks,
>> Dscho