On Sun, Feb 23, 2014 at 03:43:47PM +0700, Duy Nguyen wrote: > On Sun, Feb 23, 2014 at 2:32 PM, Robin H. Johnson <robb...@gentoo.org> 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. I think I'd prefer to delay that part then. What I'm concerned about if we do have it, is what ordering semantics there should be, eg for something like: --sparse-checkout '!X' --sparse-checkout-from F --sparse-checkout Y
Should that be [!X, *F, Y], or [*F, !X, Y], or something else? Would the option parser need to be modified to handle this? Or do we just make them mutually exclusive? The only other clean alternative would be implementing ONLY --sparse-checkout-from, and letting uses use fds creatively: --sparse-checkout-from <(echo X; echo Y) But the msysgit crowd would probably mumble complaints under their breath at me. -- Robin Hugh Johnson Gentoo Linux: Developer, Infrastructure Lead E-Mail : robb...@gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
