"Elijah Newren via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes: > From: Elijah Newren <newren@xxxxxxxxx> > > Once upon a time, Matheus wrote some patches to make > git grep [--cached | <REVISION>] ... > restrict its output to the sparsity specification when working in a > sparse checkout[1]. That effort got derailed by two things: > > (1) The --sparse-index work just beginning which we wanted to avoid > creating conflicts for > (2) Never deciding on flag and config names and planned high level > behavior for all commands. > > More recently, Shaoxuan implemented a more limited form of Matheus' > patches that only affected --cached, using a different flag name, > but also changing the default behavior in line with what Matheus did. > This again highlighted the fact that we never decided on command line > flag names, config option names, and the big picture path forward. > > The --sparse-index work has been mostly complete (or at least released > into production even if some small edges remain) for quite some time > now. We have also had several discussions on flag and config names, > though we never came to solid conclusions. Stolee once upon a time > suggested putting all these into some document in > Documentation/technical[3], which Victoria recently also requested[4]. > I'm behind the times, but here's a patch attempting to finally do that. > > Note that the "Implementation Questions" section is pretty large, > reflecting the fact that this is perhaps more RFC than proposal. Thanks for starting this. The document even in the current iteration with a large set of "questions" helped me refresh my memory on where we are in the bigger picture, and will offer us a good frame of reference.
