Re: [PATCH v2 10/18] sparse-checkout: use new update_sparsity() function
From: Derrick Stolee <hidden>
Date: 2020-03-23 18:22:57
From: Derrick Stolee <hidden>
Date: 2020-03-23 18:22:57
On 3/23/2020 2:14 PM, Elijah Newren wrote:
On Mon, Mar 23, 2020 at 11:07 AM Derrick Stolee [off-list ref] wrote:quoted
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.
Thanks!