Message ID | pull.316.v2.git.gitgitgadget@gmail.com (mailing list archive) |
---|---|
Headers | show |
Series | New sparse-checkout builtin and "cone" mode | expand |
On 9/19/2019 10:43 AM, Derrick Stolee via GitGitGadget wrote: > This series makes the sparse-checkout feature more user-friendly. While > there, I also present a way to use a limited set of patterns to gain a > significant performance boost in very large repositories. > > Sparse-checkout is only documented as a subsection of the read-tree docs > [1], which makes the feature hard to discover. Users have trouble navigating > the feature, especially at clone time [2], and have even resorted to > creating their own helper tools [3]. > > This series attempts to solve these problems using a new builtin. I haven't heard anything about this series since Elijah's careful review of the RFC. There are definitely areas where this can be made more robust, but I'd like to save those for a follow-up series. Junio: I know you didn't track this in the recent "what's cooking" list, and I don't expect you to take it until I re-roll v3 to include the .gitignore interaction I already pointed out. Thanks, -Stolee
On Tue, Oct 1, 2019 at 9:48 AM Derrick Stolee <stolee@gmail.com> wrote: > > On 9/19/2019 10:43 AM, Derrick Stolee via GitGitGadget wrote: > > This series makes the sparse-checkout feature more user-friendly. While > > there, I also present a way to use a limited set of patterns to gain a > > significant performance boost in very large repositories. > > > > Sparse-checkout is only documented as a subsection of the read-tree docs > > [1], which makes the feature hard to discover. Users have trouble navigating > > the feature, especially at clone time [2], and have even resorted to > > creating their own helper tools [3]. > > > > This series attempts to solve these problems using a new builtin. > > I haven't heard anything about this series since Elijah's careful > review of the RFC. There are definitely areas where this can be > made more robust, but I'd like to save those for a follow-up series. > > Junio: I know you didn't track this in the recent "what's cooking" > list, and I don't expect you to take it until I re-roll v3 to > include the .gitignore interaction I already pointed out. Oh, sorry, I missed this. By the way, is there any reason I wasn't cc'ed on this round after reviewing the RFC?
On 10/1/2019 12:54 PM, Elijah Newren wrote: > On Tue, Oct 1, 2019 at 9:48 AM Derrick Stolee <stolee@gmail.com> wrote: >> >> On 9/19/2019 10:43 AM, Derrick Stolee via GitGitGadget wrote: >>> This series makes the sparse-checkout feature more user-friendly. While >>> there, I also present a way to use a limited set of patterns to gain a >>> significant performance boost in very large repositories. >>> >>> Sparse-checkout is only documented as a subsection of the read-tree docs >>> [1], which makes the feature hard to discover. Users have trouble navigating >>> the feature, especially at clone time [2], and have even resorted to >>> creating their own helper tools [3]. >>> >>> This series attempts to solve these problems using a new builtin. >> >> I haven't heard anything about this series since Elijah's careful >> review of the RFC. There are definitely areas where this can be >> made more robust, but I'd like to save those for a follow-up series. >> >> Junio: I know you didn't track this in the recent "what's cooking" >> list, and I don't expect you to take it until I re-roll v3 to >> include the .gitignore interaction I already pointed out. > > Oh, sorry, I missed this. By the way, is there any reason I wasn't > cc'ed on this round after reviewing the RFC? Sorry, I forgot to modify my GitGitGadget cover letter to include you as a CC. Totally my oversight, not on purpose. Thanks, -Stolee
Derrick Stolee <stolee@gmail.com> writes: > On 9/19/2019 10:43 AM, Derrick Stolee via GitGitGadget wrote: >> This series makes the sparse-checkout feature more user-friendly. While >> there, I also present a way to use a limited set of patterns to gain a >> significant performance boost in very large repositories. >> >> Sparse-checkout is only documented as a subsection of the read-tree docs >> [1], which makes the feature hard to discover. Users have trouble navigating >> the feature, especially at clone time [2], and have even resorted to >> creating their own helper tools [3]. >> >> This series attempts to solve these problems using a new builtin. > > I haven't heard anything about this series since Elijah's careful > review of the RFC. There are definitely areas where this can be > made more robust, but I'd like to save those for a follow-up series. > > Junio: I know you didn't track this in the recent "what's cooking" > list, and I don't expect you to take it until I re-roll v3 to > include the .gitignore interaction I already pointed out. I have made a mental note that says "expecting v3, a reroll. cf. <7d87fe4b-160c-34c2-db6d-4a56fd919755@gmail.com>"; there is no existing entry to hang it below in the "what's cooking" report, though X-<.