Re: [PATCH/resent 0/9] Sparse checkout (first half)
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Oct 1, 2008, 12:09 UTC
- Message-ID
- <fcaeb9bf0810010509m4d2045e4qcc2a887c180a787@mail.gmail.com>
- In-Reply-To
- <adf1fd3d0810010425r145396b0t52cf883576da8bbd@mail.gmail.com>
On 10/1/08, Santi Béjar <santi@agolina.net> wrote:
Show 8 quoted lines
> On Wed, Oct 1, 2008 at 12:20 PM, Santi Béjar <santi@agolina.net> 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 update your checkout area. If "git clone --sparse-checkout" makes the default pattern, then "git checkout --reset-sparse" should reset the default pattern as well. The hard part is how to update default pattern with --include-sparse and --exclude-sparse. Also, people can use "git update-index" to update checkout area, which should not touch default pattern at all. Maybe just throw a warning when default pattern no longer matches the checkout area, then let them decide.
-- Duy