On 10/05/16 21:30, Junio C Hamano wrote:
> Ramsay Jones writes:
>
>> On 10/05/16 12:52, Dennis Kaarsemaker wrote:
>>> On ma, 2016-05-09 at 15:22 -0700, Junio C Hamano wrote:
It passes on one box and fails on another. They both run the same
Ubuntu 14.04
Ramsay Jones writes:
> On 10/05/16 12:52, Dennis Kaarsemaker wrote:
>> On ma, 2016-05-09 at 15:22 -0700, Junio C Hamano wrote:
>>> It passes on one box and fails on another. They both run the same
>>> Ubuntu 14.04 derivative, with same ext3 filesystem. The failing
On di, 2016-05-10 at 19:28 +0200, Dennis Kaarsemaker wrote:
> On ma, 2016-05-09 at 15:32 -0700, Junio C Hamano wrote:
> >
> > Junio C Hamano writes:
> >
> > >
> > >
> > > David Turner writes:
> > >
> > > >
> > > >
> > > > On Mon, 2016-05-09 at
On ma, 2016-05-09 at 15:32 -0700, Junio C Hamano wrote:
> Junio C Hamano writes:
>
> >
> > David Turner writes:
> >
> > >
> > > On Mon, 2016-05-09 at 14:40 -0700, Junio C Hamano wrote:
> > > >
> > > > Hmmm, I seem to be getting
> > > >
> > > >
On 10/05/16 12:52, Dennis Kaarsemaker wrote:
> On ma, 2016-05-09 at 15:22 -0700, Junio C Hamano wrote:
>> It passes on one box and fails on another. They both run the same
>> Ubuntu 14.04 derivative, with same ext3 filesystem. The failing one
>> is on a VM.
>
> Same here, except ext4 instead
On Tue, May 10, 2016 at 7:45 PM, Duy Nguyen wrote:
> If --detach is used, log_warning() can't cover die(),
> warning() or error(), most importantly die() for example because of
> bugs.
A case for redirecting warning() is because watchman-support.c uses
it. But because this
On Tue, May 10, 2016 at 6:12 AM, David Turner wrote:
> I think that's a SIGPIPE on the first git status. Weird, since I just
> added sigpipe-avoidance code (in v8). Does anyone have any idea why
> the sigchain stuff isn't doing what I think it is?
SIGPIPE code works.
On ma, 2016-05-09 at 15:22 -0700, Junio C Hamano wrote:
> It passes on one box and fails on another. They both run the same
> Ubuntu 14.04 derivative, with same ext3 filesystem. The failing one
> is on a VM.
Same here, except ext4 instead of ext3. Failing on a virtual machine,
not failing on a
On 10/05/16 00:12, David Turner wrote:
> On Mon, 2016-05-09 at 15:32 -0700, Junio C Hamano wrote:
>> Junio C Hamano writes:
>>
>>> David Turner writes:
>>>
On Mon, 2016-05-09 at 14:40 -0700, Junio C Hamano wrote:
> Hmmm, I seem to be
On Mon, 2016-05-09 at 15:32 -0700, Junio C Hamano wrote:
> Junio C Hamano writes:
>
> > David Turner writes:
> >
> > > On Mon, 2016-05-09 at 14:40 -0700, Junio C Hamano wrote:
> > > > Hmmm, I seem to be getting
> > > >
> > > > $ cat
Junio C Hamano writes:
> David Turner writes:
>
>> On Mon, 2016-05-09 at 14:40 -0700, Junio C Hamano wrote:
>>> Hmmm, I seem to be getting
>>>
>>> $ cat t/trash*7900*/err
>>> fatal: Already running
>>>
>>> after running t7900 and it fails
David Turner writes:
> On Mon, 2016-05-09 at 14:40 -0700, Junio C Hamano wrote:
>> Hmmm, I seem to be getting
>>
>> $ cat t/trash*7900*/err
>> fatal: Already running
>>
>> after running t7900 and it fails at #5, after applying
>> "index-helper: optionally
On Mon, 2016-05-09 at 14:40 -0700, Junio C Hamano wrote:
> Hmmm, I seem to be getting
>
> $ cat t/trash*7900*/err
> fatal: Already running
>
> after running t7900 and it fails at #5, after applying
> "index-helper: optionally automatically run"
It still passes for me (with or without
Hmmm, I seem to be getting
$ cat t/trash*7900*/err
fatal: Already running
after running t7900 and it fails at #5, after applying
"index-helper: optionally automatically run".
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
Formatting and patch naming fixes from Junio. No substantive changes.
David Turner (8):
index-helper: log warnings
unpack-trees: preserve index extensions
watchman: add a config option to enable the extension
index-helper: kill mode
index-helper: don't run if already running
15 matches
Mail list logo