Re: [PATCH] t5551: fix the 50,000 tag test

Torsten Bögershausen writes: > Thanks for digging, as we now know better: > do you want to squeeze in someting like this: > > s/Since the day/Since commit 5e2c7cd2/ I usually do not dig only to give suggestions to others, which will risk the time I spent to go to total waste. When I find the l

Re: [PATCH] t5551: fix the 50,000 tag test

On 2014-06-09 21.16, Junio C Hamano wrote: >> Since the day "git clone" printed "Cloning into 'too-many-refs'" to stderr, > > Thanks. It is 68b939b2 (clone: send diagnostic messages to stderr, > 2013-09-18); before it we showed the message to the standard output > stream instead. > > Will queue

Re: [PATCH] t5551: fix the 50,000 tag test

Torsten Bögershausen writes: > The first version of test 23 did simply check that no output was send > to stderr. > > Commit 5e2c7cd2 verified that the expected tags were actually cloned. > > Since the day "git clone" printed "Cloning into 'too-many-refs'" to stderr, Thanks. It is 68b939b2 (clo

[PATCH] t5551: fix the 50,000 tag test

The first version of test 23 did simply check that no output was send to stderr. Commit 5e2c7cd2 verified that the expected tags were actually cloned. Since the day "git clone" printed "Cloning into 'too-many-refs'" to stderr, the test failed because stderr was not empty. Remove the check for st