git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Haggerty <mhagger@alum.mit.edu>
To: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, Jonathan Nieder <jrnieder@gmail.com>
Cc: "Koosha Khajehmoogahi" <koosha@posteo.de>,
	"Michael J Gruber" <git@drmicha.warpmail.net>,
	"Jeff King" <peff@peff.net>, "Paul Tan" <pyokagan@gmail.com>,
	"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
	"Johannes Schindelin" <johannes.schindelin@gmx.de>,
	"Jakub Narębski" <jnareb@gmail.com>
Subject: Re: What's cooking in git.git (Apr 2015, #04; Mon, 27)
Date: Thu, 30 Apr 2015 10:21:35 +0200	[thread overview]
Message-ID: <5541E60F.1070403@alum.mit.edu> (raw)
In-Reply-To: <xmqqbni64kum.fsf@gitster.dls.corp.google.com>

On 04/30/2015 12:42 AM, Junio C Hamano wrote:
> 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

  parent reply	other threads:[~2015-04-30  8:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27 20:01 What's cooking in git.git (Apr 2015, #04; Mon, 27) Junio C Hamano
2015-04-29 22:42 ` Junio C Hamano
2015-04-29 22:50   ` Koosha Khajehmoogahi
2015-04-30  1:38     ` Junio C Hamano
2015-04-30  0:18   ` Paul Tan
2015-04-30  1:37     ` Junio C Hamano
2015-04-30  1:02   ` Jeff King
2015-04-30  1:36     ` Junio C Hamano
2015-04-30  6:55   ` Michael Haggerty
2015-04-30  8:00   ` Michael J Gruber
2015-04-30  8:21   ` Michael Haggerty [this message]
2015-04-30  1:07 ` Duy Nguyen
2015-04-30  1:35   ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5541E60F.1070403@alum.mit.edu \
    --to=mhagger@alum.mit.edu \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --cc=johannes.schindelin@gmx.de \
    --cc=jrnieder@gmail.com \
    --cc=koosha@posteo.de \
    --cc=pclouds@gmail.com \
    --cc=peff@peff.net \
    --cc=pyokagan@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).