On Sun, Feb 23, 2014 at 2:32 PM, Robin H. Johnson <robbat2@xxxxxxxxxx> wrote: >> > This patch implements easily accessible sparse checkouts during clone, >> > in the --sparse-checkout option. >> > >> > $ git clone REPO --sparse-checkout PATH >> Or take a file as input if there are lots of paths/rules. > How much demand for taking a file of rules, I don't know. I guess it depends on each repo's layout. If the layout is simple, usually you would need one or two rules so it's ok to type again and again. If it's more complicated and starts using '!' rules, it's probably best to save in a file. > and opinions of syntax to do > that vs specify on the commandline? > > --sparse-checkout-from FILE I think this one is better. But if you don't see a need for it, we can always delay implementing it until an actual use case comes up. > vs. > --sparse-checkout '<PATH' > or something other prefix character. -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html