Message ID | pull.513.v4.git.1580501775.gitgitgadget@gmail.com (mailing list archive) |
---|---|
Headers | show |
Series | Harden the sparse-checkout builtin | expand |
On Fri, Jan 31, 2020 at 12:16 PM Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com> wrote: > > This series is based on ds/sparse-list-in-cone-mode. > > This series attempts to clean up some rough edges in the sparse-checkout > feature, especially around the cone mode. > > Unfortunately, after the v2.25.0 release, we noticed an issue with the "git > clone --sparse" option when using a URL instead of a local path. This is > fixed and properly tested here. > > 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. > > Updates in V2: > > * Added C-style quoting to the output of "git sparse-checkout list" in cone > mode. > * Improved documentation. > * Responded to most style feedback. Hopefully I didn't miss anything. > * I was lingering on this a little to see if I could also fix the issue > raised in [1], but I have not figured that one out, yet. > > Update in V3: > > * Input now uses Peff's recommended pattern: unquote C-style strings over > stdin and otherwise do not un-escape input. ...and updates in V4 are? (I looked over the range-diff which definitely helps, but a summary would still be nice.)
On 1/31/2020 3:36 PM, Elijah Newren wrote: > On Fri, Jan 31, 2020 at 12:16 PM Derrick Stolee via GitGitGadget >> Update in V3: >> >> * Input now uses Peff's recommended pattern: unquote C-style strings over >> stdin and otherwise do not un-escape input. > > ...and updates in V4 are? (I looked over the range-diff which > definitely helps, but a summary would still be nice.) Sorry! I definitely should have double-checked before sending. Updates in V4: * Special-character checking now considers all glob characters ( '[', '*', '\\', '?' ) See Patches 8 and 13. * Patch 10 is is now split into two (Patches 10 and 11), to properly escape patterns and to unquote C-style strings. * The file/directory path bug reported in [1] is fixed in Patch 15. Thanks, -Stolee [1] https://lore.kernel.org/git/CADSBhNbbO=aq-Oo2MpzDMN2VAX4m6f9Jb-eCtVVX1NfWKE9zJw@mail.gmail.com/
Hi Derrick, On Mon, Feb 03, 2020 at 09:09:54AM -0500, Derrick Stolee wrote: > On 1/31/2020 3:36 PM, Elijah Newren wrote: > > On Fri, Jan 31, 2020 at 12:16 PM Derrick Stolee via GitGitGadget > >> Update in V3: > >> > >> * Input now uses Peff's recommended pattern: unquote C-style strings over > >> stdin and otherwise do not un-escape input. > > > > ...and updates in V4 are? (I looked over the range-diff which > > definitely helps, but a summary would still be nice.) > > Sorry! I definitely should have double-checked before sending. > > Updates in V4: > > * Special-character checking now considers all glob characters > ( '[', '*', '\\', '?' ) See Patches 8 and 13. > > * Patch 10 is is now split into two (Patches 10 and 11), to properly > escape patterns and to unquote C-style strings. > > * The file/directory path bug reported in [1] is fixed in Patch 15. Thanks for including these. I haven't been super active in the earlier rounds of review on this series, but I gave a thorough look to what you have in v4, and it all looks good to me. Please consider this: Reviewed-by: Taylor Blau <me@ttaylorr.com> > Thanks, > -Stolee > > [1] https://lore.kernel.org/git/CADSBhNbbO=aq-Oo2MpzDMN2VAX4m6f9Jb-eCtVVX1NfWKE9zJw@mail.gmail.com/ Thanks, Taylor
Taylor Blau <me@ttaylorr.com> writes: > On Mon, Feb 03, 2020 at 09:09:54AM -0500, Derrick Stolee wrote: > ... > Thanks for including these. I haven't been super active in the earlier > rounds of review on this series, but I gave a thorough look to what you > have in v4, and it all looks good to me. > > Please consider this: > > Reviewed-by: Taylor Blau <me@ttaylorr.com> Thanks, all.