From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: Yaron Wittenstein <yaron.wittenstein@gmail.com>,
Jeff King <peff@peff.net>,
git@vger.kernel.org
Subject: Re: [QUESTION] Tracking HEAD changes?
Date: Thu, 25 Feb 2021 08:28:03 +0100 [thread overview]
Message-ID: <YDdRgwwuvZBGuSVP@ncase> (raw)
In-Reply-To: <xmqqim6gwrf8.fsf@gitster.g>
[-- Attachment #1: Type: text/plain, Size: 757 bytes --]
On Wed, Feb 24, 2021 at 11:13:47PM -0800, Junio C Hamano wrote:
> Patrick Steinhardt <ps@pks.im> writes:
>
> > So what you're observing is simply mirroring "reality": the order in
> > which git does its things here. There can be arbitrarily many
> > transactions in a given git command, and the only way this can be
> > changed is by changing how the command operating the transcations works.
>
> In other words, ref transaction is only about changes to the refs.
> There is no such "transaction" that treats a series of operations
> like object creation and index manipulation that may happen before a
> group of refs are updated as a single unit and make it atomic.
Exactly. Thanks for putting it into better words than I did.
Patrick
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-02-25 7:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 9:12 [QUESTION] Tracking HEAD changes? Yaron Wittenstein
2021-02-23 0:38 ` Jeff King
2021-02-23 20:42 ` Jeff King
2021-02-24 20:21 ` Yaron Wittenstein
2021-02-24 21:03 ` Jeff King
2021-02-25 5:36 ` Patrick Steinhardt
2021-02-25 6:01 ` Yaron Wittenstein
2021-02-25 6:27 ` Patrick Steinhardt
2021-02-25 7:13 ` Junio C Hamano
2021-02-25 7:28 ` Patrick Steinhardt [this message]
2021-02-25 7:50 ` Yaron Wittenstein
2021-02-26 5:59 ` Jeff King
2021-02-26 20:58 ` Yaron Wittenstein
2021-03-01 9:03 ` Jeff King
2021-03-01 10:02 ` Yaron Wittenstein
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=YDdRgwwuvZBGuSVP@ncase \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=yaron.wittenstein@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.