From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
Jeff King <peff@peff.net>,
Eric Sunshine <sunshine@sunshineco.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH v2 2/8] t7004: rename ULIMIT test prerequisite to ULIMIT_STACK_SIZE
Date: Tue, 12 May 2015 14:53:31 -0700 [thread overview]
Message-ID: <xmqqegmlea3o.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAGZ79kZFC3Qr-S5dxHFf3W6FF6miNcbD8qCD48fP=PqzDhf75Q@mail.gmail.com> (Stefan Beller's message of "Mon, 11 May 2015 10:23:20 -0700")
Stefan Beller <sbeller@google.com> writes:
> On Sat, May 9, 2015 at 7:45 PM, Michael Haggerty <mhagger@alum.mit.edu> wrote:
>> From: Stefan Beller <sbeller@google.com>
>>
>> During creation of the patch series our discussion we could have a
>> more descriptive name for the prerequisite for the test so it stays
>> unique when other limits of ulimit are introduced.
>
> I must have had a bad day when trying to write this. Either words are missing
> (just insert a "revealed" after discussion on the first line) or it
I just did this s//revealed/ while re-reading the v2 series.
Thanks.
next prev parent reply other threads:[~2015-05-12 21:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 2:45 [PATCH v2 0/8] Fix atomicity and avoid fd exhaustion in ref transactions Michael Haggerty
2015-05-10 2:45 ` [PATCH v2 1/8] update-ref: test handling large transactions properly Michael Haggerty
2015-05-10 2:45 ` [PATCH v2 2/8] t7004: rename ULIMIT test prerequisite to ULIMIT_STACK_SIZE Michael Haggerty
2015-05-11 17:23 ` Stefan Beller
2015-05-12 21:53 ` Junio C Hamano [this message]
2015-05-10 2:45 ` [PATCH v2 3/8] write_ref_to_lockfile(): new function, extracted from write_ref_sha1() Michael Haggerty
2015-05-10 2:45 ` [PATCH v2 4/8] commit_ref_update(): " Michael Haggerty
2015-05-10 2:45 ` [PATCH v2 5/8] rename_ref(): inline calls to write_ref_sha1() from this function Michael Haggerty
2015-05-10 2:45 ` [PATCH v2 6/8] ref_transaction_commit(): inline call to write_ref_sha1() Michael Haggerty
2015-05-10 2:45 ` [PATCH v2 7/8] ref_transaction_commit(): remove the local flags variable Michael Haggerty
2015-05-10 2:45 ` [PATCH v2 8/8] ref_transaction_commit(): fix atomicity and avoid fd exhaustion Michael Haggerty
2015-05-11 4:30 ` [PATCH v2 0/8] Fix atomicity and avoid fd exhaustion in ref transactions Junio C Hamano
2015-05-11 6:52 ` Michael Haggerty
2015-05-11 17:10 ` Stefan Beller
2015-05-12 13:26 ` Christian Couder
2015-05-11 17:32 ` Stefan Beller
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=xmqqegmlea3o.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.net \
--cc=sbeller@google.com \
--cc=sunshine@sunshineco.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).