Re: Interpretation of '/' changed sparse-checkout

Nguyen Thai Ngoc Duy <pclouds <at> gmail.com> writes:

As a user I agree that "/" should mean "everything under the sky" and
your use case should work (i.e. it is broken in 1.7.10.2). If you can
build git, you can try the patch below. I'll submit a patch for
inclusion to git later (perhaps with optimization for this special case).

Many Thanks Duy!, that patch works so please do submit the patch.


That just leaves the other issue I noted in my original posting - if I 
exclude a path from the top-level with a 1.7.2.5 format sparse-checkout
 file, git 1.7.10.2 will exclude a sub-directory with the same name:

/
!exclude/

Unfortunately (for me), I think this is correct behaviour of 1.7.10.2 
because in 1.7.10.2 you can now do: 

/
!/exclude/
/exlucde/reinclude/

which makes sense and correctly excludes "/exclude", but not 
"/exclude/reinclude/exclude". The flexibility to have:

/
!CVS/

or something like that is required; so I don't believe should be changed?