From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff King Subject: Re: sparse checkout file with windows line endings doesn't work Date: Thu, 19 Sep 2013 23:17:05 -0400 Message-ID: <20130920031705.GA15101@sigill.intra.peff.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: Duy Nguyen , Git Mailing List To: Martin Gregory X-From: git-owner@vger.kernel.org Fri Sep 20 05:17:25 2013 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VMrDe-00065B-3J for gcvg-git-2@plane.gmane.org; Fri, 20 Sep 2013 05:17:22 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754078Ab3ITDRQ (ORCPT ); Thu, 19 Sep 2013 23:17:16 -0400 Received: from cloud.peff.net ([50.56.180.127]:40876 "EHLO peff.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753965Ab3ITDRP (ORCPT ); Thu, 19 Sep 2013 23:17:15 -0400 Received: (qmail 22203 invoked by uid 102); 20 Sep 2013 03:17:14 -0000 Received: from c-71-63-4-13.hsd1.va.comcast.net (HELO sigill.intra.peff.net) (71.63.4.13) (smtp-auth username relayok, mechanism cram-md5) by peff.net (qpsmtpd/0.84) with ESMTPA; Thu, 19 Sep 2013 22:17:14 -0500 Received: by sigill.intra.peff.net (sSMTP sendmail emulation); Thu, 19 Sep 2013 23:17:05 -0400 Content-Disposition: inline In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On Fri, Sep 20, 2013 at 11:22:01AM +0930, Martin Gregory wrote: > When something goes wrong, there appears to be no way to understand what > git thinks it's reading. I'm not sure if such a way, if it existed, would help with > trailing spaces, but if you could say > > git read-tree -muv HEAD > > and it would say > > reading '.git\info\sparse-checkout'... > rule '/CONFIGURATION ' - no matches I don't think you can do that in the general case of read-tree. You may have sparse paths that exist in some commits, but not others. As you move around in history, a sparse entry that does not match might do so because it is poorly written, or it might do so because you just don't happen to have any matching paths in the commit you are moving to. The former is a problem, but warning on the latter would be useless noise. -Peff