From: Jeff King <peff@peff.net>
To: Martin Gregory <marting@adelaideinterim.com.au>
Cc: Duy Nguyen <pclouds@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: sparse checkout file with windows line endings doesn't work
Date: Thu, 19 Sep 2013 23:17:05 -0400 [thread overview]
Message-ID: <20130920031705.GA15101@sigill.intra.peff.net> (raw)
In-Reply-To: <SDZYTDk4NyMxKC4hPVQvMjM1MDUxNjg3@IBMLT4>
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
next prev parent reply other threads:[~2013-09-20 3:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACsJy8BSqJjxNwz=p7sGO2jfByLfngvN0yq55URXkX=yV+OEfQ@mail.gmail.com>
[not found] ` <SDZYRFhOTCk2PDAuPVQvMjI4MjE1ODkw@IBMLT4>
2013-09-20 1:15 ` re[4]: sparse checkout file with windows line endings doesn't work Duy Nguyen
2013-09-20 1:52 ` re[6]: " Martin Gregory
2013-09-20 2:28 ` Duy Nguyen
2013-09-20 3:17 ` Jeff King [this message]
2013-09-20 3:24 ` re[2]: " Martin Gregory
2013-09-20 3:38 ` Jeff King
2013-09-20 3:52 ` re[2]: " Martin Gregory
2013-09-20 18:06 ` Junio C Hamano
2013-09-16 13:20 Martin Gregory
2013-09-17 11:35 ` Duy Nguyen
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=20130920031705.GA15101@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=marting@adelaideinterim.com.au \
--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;
as well as URLs for NNTP newsgroup(s).