Re: [RFC PATCH 00/12] Sparse checkout

["Nguyen Thai Ngoc Duy" <pclouds@gmail.com>]

On 7/23/08, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
>
>  On Wed, 23 Jul 2008, Nguyen Thai Ngoc Duy wrote:
>
>  > On 7/23/08, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>  >
>
> > >  On Wed, 23 Jul 2008, Nguyen Thai Ngoc Duy wrote:
>  > >
>  > >  > So in short, sparse prefix will be stored in config,
>  > >  > core.sparsecheckout.
>  > >
>  > > Do you really think the prefix should be stored anywhere else than the
>  > > index?
>  > >
>  > > With core.sparseCheckout you have to introduce a _sh*tload_ of config
>  > > loaders.
>  > >
>  > > And with core.sparseCheckout you are at the whim of the user, since
>  > > .git/config is _supposed_ to be user-editable.
>  > >
>  > > From a logical point of view, I'd say that the sparse prefix has
>  > > nothing to do with the "configuration" of the local repository.
>  >
>  > Well, whatever place. I chose .git/config because I did not want to
>  > introduce a new config place. But then how about .git/sparsecheckout?
>
>
> No, I did mean the index.  This is an attribute of the index: either it is
>  sparsely checked out or not.  You can even have multiple indices
>  (switching between them by setting GIT_INDEX_FILE) which have different
>  prefixes.

I don't think so. It's a mask for workdir, right? If you save it it
index, you can switch index and the prefix as well, but workdir only
has several subtrees that do not fit any other prefix than the
original prefix.

>  Ciao,
>  Dscho "who seems to recall that the first series was much less intrusive"

The first series only took care of index, so yes it's simpler.
-- 
Duy