Re: [PATCH v2 10/18] sparse-checkout: use new update_sparsity() function
On 3/23/2020 2:14 PM, Elijah Newren wrote:
Show 10 quoted lines
> On Mon, Mar 23, 2020 at 11:07 AM Derrick Stolee <stolee@gmail.com> wrote:
>>
>> Should the "error" messages we grep for be more specific? Are they
>> the same as the "Cannot update sparse checkout"?
>
> The two lines are checking for the same message, it's just that the
> error message is split across multiple lines and thus requires two
> greps. The error messages are actually a bit of a mess, particularly
> when they are triggered for multiple paths. That's something that
> subsequent commits will clean up.
I see that now! The very next commit cleans this up nicely.
> I can add a note about this to the commit message.
Derrick Stolee <stolee@gmail.com>