re[2]: sparse checkout file with windows line endings doesn't work

2013-09-19 Thread Martin Gregory
>> 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 >>

re[2]: sparse checkout file with windows line endings doesn't work

2013-09-19 Thread Martin Gregory
>> 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 wi

re[6]: sparse checkout file with windows line endings doesn't work

2013-09-19 Thread Martin Gregory
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

re[2]: sparse checkout file with windows line endings doesn't work

2013-09-19 Thread Martin Gregory
checkout.tar.gz .git/info/sparse-checkout in gitbash shell on Windows. Regards, Martin -- Martin Gregory Senior Consultant, Adelaide Interim P: +61 8 7200 5350 M: +61 402 410 971 F: +61 8 7200 3725 sparsecheckout.tar.gz Description: Binary data

re[2]: sparse checkout file with windows line endings doesn't work

2013-09-17 Thread Martin Gregory
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

re[2]: Issue with sparse checkout

2013-09-17 Thread Martin Gregory
Hi Duy, Thanks for taking a look. >> > So it does feel like a bug to me: why are files with ^S set remaining in >> the >> > working version after >> > >> > git read-tree -mu HEAD >> > >> > ? >> >> I don't know. Maybe the bits are set, but then the remove operation >> fails (silently). I

Re: Issue with sparse checkout

2013-09-16 Thread Martin Gregory
An additional note. I did git ls-files -v | grep ^S and I can see that the files that remain in the working version have the ^S bit set. So it does feel like a bug to me: why are files with ^S set remaining in the working version after git read-tree -mu HEAD ? Regards, Martin -- T

sparse checkout file with windows line endings doesn't work

2013-09-16 Thread Martin Gregory
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

Issue with sparse checkout

2013-09-16 Thread Martin Gregory
I wonder if you can advise me if this is a bug with sparsecheckout, or if not what I'm doing wrong: http://pastebin.com/HUaWrtef Basically, I believe that when I do git read-tree, I should be left with only the directory CONFIGURATION. However, DV_TDM remains. But it's status seems to be "ind