On 10/1/08, Santi Béjar <santi@xxxxxxxxxxx> wrote:> On Wed, Oct 1, 2008 at 12:20 PM, Santi Béjar <santi@xxxxxxxxxxx> wrote:> > Not in this half but I've seen that you added a --default-sparse flag> > to "git clone". I think it is useless as mostly always the one given> > in -sparse-checkout should be used.>>> To be more precise, whenever you do "git clone --sparse-checkout" you> will want it to be the default sparse pattern.
Yes, if only the default pattern gets updated properly when you updateyour checkout area. If "git clone --sparse-checkout" makes the defaultpattern, then "git checkout --reset-sparse" should reset the defaultpattern as well. The hard part is how to update default pattern with--include-sparse and --exclude-sparse. Also, people can use "gitupdate-index" to update checkout area, which should not touch defaultpattern at all. Maybe just throw a warning when default pattern nolonger matches the checkout area, then let them decide.-- Duy��.n��������+%������w��{.n��������n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�m
