Git development
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH 00/12] Sparse checkout
Date: Wed, 23 Jul 2008 17:55:14 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.1.00.0807231753240.8986@racer> (raw)
In-Reply-To: <fcaeb9bf0807230921m114f5ae0ybfec4917432d6dc7@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1185 bytes --]

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, Nguyễn Thái Ngọc 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.

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

  reply	other threads:[~2008-07-23 16:56 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-23 14:55 [RFC PATCH 00/12] Sparse checkout Nguyễn Thái Ngọc Duy
2008-07-23 15:38 ` Nguyen Thai Ngoc Duy
2008-07-23 16:15 ` Johannes Schindelin
2008-07-23 16:21   ` Nguyen Thai Ngoc Duy
2008-07-23 16:55     ` Johannes Schindelin [this message]
2008-07-24  8:27       ` Nguyen Thai Ngoc Duy
2008-07-24 12:42         ` Johannes Schindelin
2008-07-24 13:29           ` Nguyen Thai Ngoc Duy
2008-07-24 13:44             ` Johannes Schindelin
2008-07-24 13:50               ` Nguyen Thai Ngoc Duy
2008-07-24 16:22                 ` Avery Pennarun
2008-07-24 16:38                   ` Johannes Schindelin
2008-07-24 18:59                   ` Nguyen Thai Ngoc Duy
2008-08-03 18:37       ` Jan Hudec
2008-08-03 20:48         ` Johannes Schindelin
2008-08-04 12:29         ` Nguyen Thai Ngoc Duy
2008-07-24  8:24 ` James Pickens
2008-07-24  9:00   ` Nguyen Thai Ngoc Duy
2008-07-24 17:59     ` James Pickens
2008-07-24 23:23       ` Nguyen Thai Ngoc Duy
2008-07-24 23:38         ` James Pickens
2008-07-24  9:35 ` Jakub Narebski
2008-07-24 10:58   ` Nguyen Thai Ngoc Duy
2008-07-24 20:01     ` Jakub Narebski
2008-07-24 23:21       ` Nguyen Thai Ngoc Duy
2008-07-25 14:53         ` Avery Pennarun
2008-07-25  0:07       ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.1.00.0807231753240.8986@racer \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox