Jeff King writes:
> 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
>
>> I don't mind a special option to turn this on for debugging, but the
>> normal "-v" for read-tree is not "show me random noise", but rather
>> "keep me occupied with a progress bar". If it were triggered by two or
>> more "-v" options (which could also contain other debugging output), I'd
>>
On Fri, Sep 20, 2013 at 12:54:45PM +0930, Martin Gregory wrote:
> >> 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
> >>
>> 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
>> >
>> >
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
On Fri, Sep 20, 2013 at 8:52 AM, Martin Gregory
wrote:
> Something that would help is an easier way to debug sparse-checkout rules.
>
> 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 wit
Thanks Duy for the fast response.
> Anyway there is a trailing space at the
>> end of the rule. This is the content of your sparse checkout file in C
>> syntax
>>
>> "/CONFIGURATION\x20\r\n"
>>
>> Maybe we could warn about trailing spaces.. Stripping them
>> automatically is a possibility, bu
On Fri, Sep 20, 2013 at 7:01 AM, Martin Gregory
wrote:
> Hi Duy ,
>
> re: [file created in gitbash]
>
>>> Thanks. Please send me the file created by windows shell. I suspected
>>> that windows shell may save it in some funny encoding like utf-16..
>
>
> Strangely, I had sent the file created by
Hi Duy,
>> And it does work for me with CRLF endings (again tested on Linux). Can
>> you send me your sparse-checkout file? Zip it if needed.
sparse-checkout created with
echo /CONFIGURATION > .git\info\sparse-checkout
on Windows.
Attached file created with
tar cvzf sparsecheckout.tar.gz .g
Hi Duy,
Thanks again for taking a look at these two reports.
>> And it does work for me with CRLF endings (again tested on Linux).
Yes, will do.
I will try, myself, on Linux, as well. It seems quite conceivable its the
sort of thing that only happens under Windows.
Regards,
Martin
--
To un
On Mon, Sep 16, 2013 at 8:20 PM, Martin Gregory
wrote:
> Hi,
>
> Please see http://pastebin.com/zMXvvXuy
>
> It shows that if the .git/info/sparsecheckout file is in windows format
> (windows line ending) then it doesn't work.
And it does work for me with CRLF endings (again tested on Linux). Ca
Hi,
Please see http://pastebin.com/zMXvvXuy
It shows that if the .git/info/sparsecheckout file is in windows format
(windows line ending) then it doesn't work.
Thanks for any advice.
This is git 1.8.3.msysgit.0
Martin
--
To unsubscribe from this list: send the line "unsubscribe git" in
the b
12 matches
Mail list logo
