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-17 Thread Duy Nguyen
On Tue, Sep 17, 2013 at 5:46 AM, Martin Gregory wrote: > 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 ve

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

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