[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] [PATCH] Broken migration code? (Merging branch to
From: |
Zack Weinberg |
Subject: |
Re: [Monotone-devel] [PATCH] Broken migration code? (Merging branch to allow duplicate key names, have certs use key hash) |
Date: |
Mon, 24 Aug 2009 09:53:05 -0700 |
On Mon, Aug 24, 2009 at 1:38 AM, Stephen
Leake<address@hidden> wrote:
>> Possible proper fix:
>>
>> -m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES])
>> +m4_ifdef([AM_SILENT_RULES],
>> + [AM_SILENT_RULES],
>> + [AM_DEFAULT_VERBOSITY=1
>> + AC_SUBST([AM_DEFAULT_VERBOSITY])])
>>
>> in configure.ac.
>
> Yes, that fixes it.
Thanks, I'll commit that shortly.
> Another fix is to delete the lines labeled "verbosity goo" in
> Makefile.am. Do we really need them? At one point in investigating
> this, I deleted them, and 'make check' succeeded.
Try "make clean; make V=0" on the machine with automake 1.11 before
you say that. :-)
zw
- Re: [Monotone-devel] Merging branch to allow duplicate key names, have certs use key hash, (continued)
- Re: [Monotone-devel] Merging branch to allow duplicate key names, have certs use key hash, Timothy Brownawell, 2009/08/20
- [Monotone-devel] [PATCH] Broken migration code? (Merging branch to allow duplicate key names, have certs use key hash), Timothy Brownawell, 2009/08/23
- Re: [Monotone-devel] [PATCH] Broken migration code? (Merging branch to allow duplicate key names, have certs use key hash), Stephen Leake, 2009/08/23
- Re: [Monotone-devel] [PATCH] Broken migration code? (Merging branch to allow duplicate key names, have certs use key hash), Zack Weinberg, 2009/08/23
- Re: [Monotone-devel] [PATCH] Broken migration code? (Merging branch to allow duplicate key names, have certs use key hash), Stephen Leake, 2009/08/24
- Re: [Monotone-devel] [PATCH] Broken migration code? (Merging branch to allow duplicate key names, have certs use key hash),
Zack Weinberg <=
- Re: [Monotone-devel] [PATCH] Broken migration code? (Merging branch to allow duplicate key names, have certs use key hash), Stephen Leake, 2009/08/24