Michael J Gruber writes:
> I don't mind carrying this locally and retrying without for the next
> round of notmuch updates. Having the patch here on-list may help
> someone else in the future in any case.
OK, I suggest you do that for now. I'm not categorically opposed to
(some version of) the
On Wed, Feb 16 2022, Tomi Ollila wrote:
>
> I'd not merge this NOTMUCH_NEW_OPTIONS=--full-scan ;D too eagerly
> ... I'd like we really knew the reason (which is then written in
> commit message)
I seem I did not get my message above (or why the ;D is there)
expressed clear enough -- the idea
On Wed, Feb 16 2022, Michael J. Gruber wrote:
> David Bremner venit, vidit, dixit 2022-02-16 14:04:17:
>> Michael J Gruber writes:
>>
>> > Some build infrastructure appears to habe problems with mtime/stat,
>>
>> have
>
> Huh, this looks as if my mother tongue slipped in, while it's just key
>
David Bremner venit, vidit, dixit 2022-02-16 14:04:17:
> Michael J Gruber writes:
>
> > Some build infrastructure appears to habe problems with mtime/stat,
>
> have
Huh, this looks as if my mother tongue slipped in, while it's just key
proximity.
> > leading to spurious failures (noticed on
Michael J Gruber writes:
> Some build infrastructure appears to habe problems with mtime/stat,
have
> leading to spurious failures (noticed on s390x and aarch64 with epel8).
> Allow the test suite to be run with --full-sync so that release builds
> can use the test suite while avoiding
Some build infrastructure appears to habe problems with mtime/stat,
leading to spurious failures (noticed on s390x and aarch64 with epel8).
Allow the test suite to be run with --full-sync so that release builds
can use the test suite while avoiding spurious failures.
Signed-off-by: Michael J
