On 1/15/2020 2:16 PM, Junio C Hamano wrote: > "Derrick Stolee via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes: > >> Also, let's improve Git's response to these more complicated scenarios: >> >> 1. Running "git sparse-checkout init" in a worktree would complain because >> the "info" dir doesn't exist. >> 2. Tracked paths that include "*" and "" in their filenames. >> 3. If a user edits the sparse-checkout file to have non-cone pattern, such >> as "*" anywhere or "" in the wrong place, then we should respond >> appropriately. That is: warn that the patterns are not cone-mode, then >> revert to the old logic. > > It seems somebody ate a letter to make "<some letter>" into "" an > empty string, so I cannot quite grok the above list---two out of > three bullet points are not quite readable. In 2., the "" should be "\". In 3., the "*" and "" should be "**" and "*" respectively. These are things that are being collapsed by GitHub's markdown processing. Sorry that this affects GitGitGadget's cover letter. By escaping appropriately, these show up correctly and hopefully will be fixed in v2. -Stolee
