From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Nguyen Thai Ngoc Duy" Subject: Re: What's cooking in git.git (Nov 2008, #06; Wed, 26) Date: Fri, 12 Dec 2008 23:08:39 +0700 Message-ID: References: <7v7i6qc8r0.fsf@gitster.siamese.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: "Junio C Hamano" , "Shawn O. Pearce" , "Johannes Schindelin" , git@vger.kernel.org To: "Daniel Barkalow" X-From: git-owner@vger.kernel.org Fri Dec 12 17:10:11 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 1LBAaV-00035F-NG for gcvg-git-2@gmane.org; Fri, 12 Dec 2008 17:10:00 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757407AbYLLQIm (ORCPT ); Fri, 12 Dec 2008 11:08:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757538AbYLLQIm (ORCPT ); Fri, 12 Dec 2008 11:08:42 -0500 Received: from fg-out-1718.google.com ([72.14.220.154]:2168 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757133AbYLLQIl (ORCPT ); Fri, 12 Dec 2008 11:08:41 -0500 Received: by fg-out-1718.google.com with SMTP id 19so732424fgg.17 for ; Fri, 12 Dec 2008 08:08:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=+VCflO+rYnTEk/basX2cf5Rkx/i6hDHCzbprEid86vA=; b=Tsg/XvAZDb3hcaPdj0tOIklT02Y89ew521FlIgmfITUT0VA1Aa2VP5oJF9TKeysyYf 4ZjPHyQQQrAn9D8iM4muhDUPgj5IGyNaJwMGXwj7Wt/zndMFtl5C0p30Fy9Yi5XIO1hq MpJ6hSho4XiyNbf9xPEShFVu9fwhVy78ZpOtI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=Mxbb+D721BMPF/njiB0e0gYTIU9CDGWkAUqUmvDIS2Q2We1X+m5x+rxcx3vFP65vGM XqGgFfNdRr+gFmLOa1lljX0XbaZ7Cm6eqBjFsdyMFzpMiRDBwt2V9NcWOyBz5+vK9jGC +O6ULLwuuJAQsGnmVIht8FKHokFx3icxavOVY= Received: by 10.86.4.14 with SMTP id 14mr2099974fgd.27.1229098119554; Fri, 12 Dec 2008 08:08:39 -0800 (PST) Received: by 10.86.87.14 with HTTP; Fri, 12 Dec 2008 08:08:39 -0800 (PST) In-Reply-To: Content-Disposition: inline Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On 12/12/08, Daniel Barkalow wrote: > > Well, if you set core.defaultsparse properly, those files should > > appear/disappear as you wish (and as of now if you define your > > checkout area with "git checkout --{include-,exclude-,}sparse" then > > core.defaultsparse should be updated accordingly). I don't say > > core.defaultsparse is perfect. > > > Right, so in order to get reasonable behavior, the user must use > --{include,exclude}-sparse. I think that this should be the *default* > behavior, and probably the *only porcelain-supported* behavior, because > otherwise it's confusing. It's pretty hard (or intrusive) to enforce such behaviour. How about showing files that does not match core.defaultsparse in "git status" along with instructions how to add them to core.defaultsparse? That way people can keep it consistent and less modification to current code. -- Duy