Re: [PATCH v5 3/5] core.fsync: introduce granular fsync control
Neeraj Singh <nksingh85@gmail.com> writes:
Show 10 quoted lines
>> > At the conclusion of this series, I defined 'default' as an aggregate
>> > option that includes
>> > the platform default. I'd prefer not to have any statefulness of the
>> > core.fsync setting so
>> > that there is less confusion about the final fsync configuration.
>>
>> Then scratch your preference ;-)
>
> Just to clarify, linguistically, by 'scratch' do you mean that I should drop
> my preference
> Is there a well-defined place where we know that configuration processing
> is complete? The most obvious spot to me to integrate these two values would
> be the first time we need to figure out the fsync state.
That sounds like a good place.
Junio C Hamano <gitster@pobox.com>