Re: What's cooking in git.git (Apr 2015, #04; Mon, 27)

From: Michael Haggerty <mhagger@alum.mit.edu>
Date: Apr 30, 2015, 08:21 UTC
Message-ID: <5541E60F.1070403@alum.mit.edu>
In-Reply-To: <xmqqbni64kum.fsf@gitster.dls.corp.google.com>

On 04/30/2015 12:42 AM, Junio C Hamano wrote:

Show 24 quoted lines

> Junio C Hamano <gitster@pobox.com> writes:
> 
>> Here are the topics that have been cooking.  Commits prefixed with
>> '-' are only in 'pu' (proposed updates) while commits prefixed with
>> '+' are in 'next'.
>> ...
> 
> There are a handful of topics that are almost there but not
> finished.  Could the topic owners and area submaintainers who are
> involved in them report their current status soonish, please, to
> help me decide to keep or discard them?
> 
> [...]
>> * mh/fdopen-with-retry (2015-03-06) 6 commits
>>  - buffer_fdinit(): use fdopen_with_retry()
>>  - update_info_file(): use fdopen_with_retry()
>>  - copy_to_log(): use fdopen_with_retry()
>>  - fdopen_lock_file(): use fdopen_with_retry()
>>  - SQUASH??? $gmane/264889
>>  - xfdopen(): if first attempt fails, free memory and try again
>>
>>  Various parts of the code where they call fdopen() can fail when
>>  they run out of memory; attempt to proceed by retrying the
>>  operation after freeing some resource.

Since we haven't heard anything from Jonathan (who originally suggested this change) and since nobody else seems to be able to muster much enthusiasm for it, let's discard this one. It's probably too much code to invest in a theoretical problem that AFAIK has never been observed.

Michael

-- 
Michael Haggerty
mhagger@alum.mit.edu