git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [QUESTION] Tracking HEAD changes?

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 25, 2021, 07:13 UTC
Message-ID
<xmqqim6gwrf8.fsf@gitster.g>
In-Reply-To
<YDdDUILUUXA1ytva@ncase>
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.

Previous: Patrick SteinhardtNext: Patrick Steinhardt
Message 9 of 15 in “[QUESTION] Tracking HEAD changes?”
  1. Yaron WittensteinFeb 22, 2021
  2. Jeff KingFeb 23, 2021
  3. Jeff KingFeb 23, 2021
  4. Yaron WittensteinFeb 24, 2021
  5. Jeff KingFeb 24, 2021
  6. Patrick SteinhardtFeb 25, 2021
  7. Yaron WittensteinFeb 25, 2021
  8. Patrick SteinhardtFeb 25, 2021
  9. Junio C HamanoFeb 25, 2021
  10. Patrick SteinhardtFeb 25, 2021
  11. Yaron WittensteinFeb 25, 2021
  12. Jeff KingFeb 26, 2021
  13. Yaron WittensteinFeb 26, 2021
  14. Jeff KingMar 1, 2021
  15. Yaron WittensteinMar 1, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.