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

[PATCH 0/3] Use ref transactions for fetch

From
Ronnie Sahlberg <sahlberg@google.com>
Date
Apr 22, 2014, 18:45 UTC
Message-ID
<1398192327-21302-1-git-send-email-sahlberg@google.com>

This change is based on the previous ref transaction patches. This is sent as a separate patch series since it implements a lot more non-trivial changes to the behaviour than the previous patches and thus can use more detailed review.

Update fetch.c to use ref transactions when performing updates. Use a single ref transaction for all updates and only commit the transaction if all other checks and oeprations have been successful. This makes the ref updates during a fetch (mostly) atomic.

Ronnie Sahlberg (3):
  fetch.c: clear errno before calling functions that might set it
  fetch.c: change s_update_ref to use a ref transaction
  fetch.c: use a single ref transaction for all ref updates
 builtin/fetch.c | 39 ++++++++++++++++++++++-----------------
 1 file changed, 22 insertions(+), 17 deletions(-)
-- 
1.9.1.518.g16976cb.dirty
Next: Ronnie Sahlberg
Message 1 of 14 in “Use ref transactions for fetch”
  1. 0/3 Use ref transactions for fetchRonnie Sahlberg, Apr 22, 2014
  2. 1/3 fetch.c: clear errno before calling functions that might set itRonnie Sahlberg, Apr 22, 2014
  3. Eric SunshineApr 23, 2014
  4. Ronnie SahlbergApr 24, 2014
  5. 2/3 fetch.c: change s_update_ref to use a ref transactionRonnie Sahlberg, Apr 22, 2014
  6. Eric SunshineApr 23, 2014
  7. Ronnie SahlbergApr 24, 2014
  8. 3/3 fetch.c: use a single ref transaction for all ref updatesRonnie Sahlberg, Apr 22, 2014
  9. Eric SunshineApr 23, 2014
  10. Ronnie SahlbergApr 24, 2014
  11. Michael HaggertyMay 5, 2014
  12. Ronnie SahlbergMay 5, 2014
  13. Junio C HamanoMay 6, 2014
  14. Michael HaggertyMay 6, 2014

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.