From: Junio C Hamano <gitster@pobox•com>
To: Ronnie Sahlberg <sahlberg@google•com>
Cc: Michael Haggerty <mhagger@alum•mit.edu>,
"git\@vger.kernel.org" <git@vger•kernel.org>
Subject: Re: [PATCH v4 0/3] Make update refs more atomic
Date: Wed, 16 Apr 2014 14:42:09 -0700 [thread overview]
Message-ID: <xmqqtx9teytq.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAL=YDWnHtPedxYmpycgSybZA=CmdD55XQAFdA-Bs_42bk2Z0Tg@mail.gmail.com> (Ronnie Sahlberg's message of "Wed, 16 Apr 2014 14:31:17 -0700")
Ronnie Sahlberg <sahlberg@google•com> writes:
>> I am not sure if that is the right way to go, or instead change all
>> create/update/delete to take locks without adding a new primitive.
>
> ack.
Hmph. When I say "I am not sure", "I dunno", etc., I do mean it.
Did you mean by "Ack" "I do not know, either", or "I think it is
better to take locks early everywhere"?
next prev parent reply other threads:[~2014-04-16 21:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 18:29 [PATCH v4 0/3] Make update refs more atomic Ronnie Sahlberg
2014-04-14 18:29 ` [PATCH v4 1/3] refs.c: split writing and commiting a ref into two separate functions Ronnie Sahlberg
2014-04-15 11:17 ` Michael Haggerty
2014-04-14 18:29 ` [PATCH v4 2/3] refs.c: split delete_ref_loose() into a separate flag-for-deletion and commit phase Ronnie Sahlberg
2014-04-15 17:19 ` Michael Haggerty
2014-04-14 18:29 ` [PATCH v4 3/3] refs.c: change ref_transaction_commit to run the commit loops once all work is finished Ronnie Sahlberg
2014-04-14 20:24 ` [PATCH v4 0/3] Make update refs more atomic Junio C Hamano
2014-04-15 16:41 ` Ronnie Sahlberg
2014-04-15 6:36 ` Michael Haggerty
2014-04-15 16:33 ` Ronnie Sahlberg
2014-04-15 20:32 ` Michael Haggerty
2014-04-16 17:11 ` Ronnie Sahlberg
2014-04-16 19:31 ` Junio C Hamano
2014-04-16 21:31 ` Ronnie Sahlberg
2014-04-16 21:42 ` Junio C Hamano [this message]
2014-04-16 21:51 ` Michael Haggerty
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=xmqqtx9teytq.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=mhagger@alum$(echo .)mit.edu \
--cc=sahlberg@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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