From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Schindelin Subject: Re: [RFC PATCH 00/12] Sparse checkout Date: Wed, 23 Jul 2008 17:55:14 +0100 (BST) Message-ID: References: <20080723145518.GA29035@laptop> Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323329-1646694251-1216832115=:8986" Cc: git@vger.kernel.org To: Nguyen Thai Ngoc Duy X-From: git-owner@vger.kernel.org Wed Jul 23 18:56:15 2008 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1KLhdP-0008UI-5K for gcvg-git-2@gmane.org; Wed, 23 Jul 2008 18:56:15 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752810AbYGWQzP (ORCPT ); Wed, 23 Jul 2008 12:55:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752675AbYGWQzO (ORCPT ); Wed, 23 Jul 2008 12:55:14 -0400 Received: from mail.gmx.net ([213.165.64.20]:60081 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751869AbYGWQzN (ORCPT ); Wed, 23 Jul 2008 12:55:13 -0400 Received: (qmail invoked by alias); 23 Jul 2008 16:55:11 -0000 Received: from grape.st-and.ac.uk (EHLO grape.st-and.ac.uk) [138.251.155.28] by mail.gmx.net (mp057) with SMTP; 23 Jul 2008 18:55:11 +0200 X-Authenticated: #1490710 X-Provags-ID: V01U2FsdGVkX185Y8MnWkQ567adUyKLHoyzeP2yqWEcYMZFCHXczz BgWZMw7gaf/wBy X-X-Sender: gene099@racer In-Reply-To: User-Agent: Alpine 1.00 (DEB 882 2007-12-20) X-Y-GMX-Trusted: 0 X-FuHaFi: 0.64 Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-1646694251-1216832115=:8986 Content-Type: TEXT/PLAIN; charset=UTF-8 Content-Transfer-Encoding: 8BIT Hi, On Wed, 23 Jul 2008, Nguyen Thai Ngoc Duy wrote: > On 7/23/08, Johannes Schindelin 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" --8323329-1646694251-1216832115=:8986--