bug: sparse config interpretation incorrectness in 2.8.0-rc2

2016-03-19 Thread Durham Goode
Using git 2.8.0-rc2, given a repo with the following files: - one/hideme - one/donthide - two/foo A sparse config of: cat > .git/info/sparse-checkout

Re: bug: sparse config interpretation incorrectness in 2.8.0-rc2

2016-03-19 Thread Durham Goode
On 3/17/16 12:22 AM, Junio C Hamano wrote: Durham Goode <dur...@fb.com> writes: Using git 2.8.0-rc2, given a repo with the following files: - one/hideme - one/donthide - two/foo A sparse config of: cat > .git/info/sparse-checkout < 2.6 is a tad too old as a reference, as the &

Re: [PATCH 3/2] dir.c: fix dir re-inclusion rules with "NODIR" and "MUSTBEDIR"

2016-03-19 Thread Durham Goode
On 3/17/16 10:40 PM, Duy Nguyen wrote: On Fri, Mar 18, 2016 at 11:51 AM, Durham Goode <dur...@fb.com> wrote: On 3/17/16 4:49 PM, Junio C Hamano wrote: Thanks for these 5 patches, two of which need to be discarded ;-). I think you can pick either one of 1/2, pick the one that says &qu

Re: bug: sparse config interpretation incorrectness in 2.8.0-rc2

2016-03-19 Thread Durham Goode
On 3/16/16 5:56 PM, Duy Nguyen wrote: On Wed, Mar 16, 2016 at 05:09:23PM -0700, Durham Goode wrote: Using git 2.8.0-rc2, given a repo with the following files: - one/hideme - one/donthide - two/foo A sparse config of: cat > .git/info/sparse-checkout < Thank you. This should fix it. I t

Re: [PATCH 3/2] dir.c: fix dir re-inclusion rules with "NODIR" and "MUSTBEDIR"

2016-03-18 Thread Durham Goode
On 3/17/16 4:49 PM, Junio C Hamano wrote: Thanks for these 5 patches, two of which need to be discarded ;-). I think you can pick either one of 1/2, pick the one that says "non-NULL" (as opposed to "something") in the log message for 2/2. Durham, does it fix your issues if you apply the 1/2 and

bug: git-svn seg fault during 'git svn fetch' due to perl 5.10

2013-01-17 Thread Durham Goode
In git 1.8.1, when we do 'git svn fetch' on a large repo, we're seeing a seg fault. It's caused by git-svn trying to parse a large yaml file (introduced in https://github.com/git/git/commit/68f532f4ba888f277637a94b4a49136054df0540 ) which encounters a perl regex stack overflow bug that was