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

[PATCH 0/4] Using transactions for the reflog

From
Stefan Beller <sbeller@google.com>
Date
Nov 27, 2014, 05:34 UTC
Message-ID
<1417066485-24921-1-git-send-email-sbeller@google.com>
In-Reply-To
<20141120181701.GB15945@google.com>

This is the core part of the refs-transactions-reflog series[1], which was in discussion for a bit already.

The idea is to have the reflog being part of the transactions, which the refs are already using, so the we're moving towards a database like API in the long run. This makes git easier to maintain as well as opening the possibility to replace the backend with a real database.

The first patch is essentially just some sed magic with reformatting the code, so the naming convention fits better, because the transactions will handle both the refs as well as the reflog after this series.

The second patch introduces a new enum field to indicate, if we deal with a ref or with a reflog entry in the transaction.

The meat and most of the lines of code are found in the 3rd patch. We introduce a rather lengthy function transaction_update_reflog, which prepares all the reflog related changes. The transaction_commit function will then also put the reflog changes in place in a "best effort" atomic way. Unlike in previous versions, we don't keep all the reflog in memory, but use a temporary file in $GIT_DIR instead and the update can be done using an atomic rename(...).

One of my todos is to make the error handling in the transaction_update_reflog function a bit less repetitive either during the discussion of this series or as a follow up.

The last patch in this series makes use of the transaction system in the user facing code, when running "git reflog expire" for example.

I'd appreciate any comments. 

Apart from sending feedback on the list, you can find this series at github[2] embedded into the longer version of the series. In that series at github there are a few more patches[3], which are already reviewed and residing in Junios repository or considered trivial cleanups.

Thanks, Stefan

[1] http://comments.gmane.org/gmane.comp.version-control.git/259712
[2] https://github.com/stefanbeller/git/commits/todo_sb13_ref-transactions-reflog-as-file
[3] The first 2 commits on top of Git 2.2-rc3 are origin/sb/ref-transaction-unify-to-update, 
    the third is in origin/sb/log-ref-write-fd, then comes this series in 4 patches. 
    The remaining latest 4 patches are clean up patches, mainly removing parts from the refs API
    which are no longer in use. I do not include these in this patch series, as I don't want to
    scare people away with a huge bulk of messages.
Ronnie Sahlberg (4):
  refs.c: rename the transaction functions
  refs.c: add a new update_type field to ref_update
  refs.c: add a transaction function to append a reflog entry
  reflog.c: use a reflog transaction when writing during expire
 branch.c               |  13 +--
 builtin/commit.c       |  10 +-
 builtin/fetch.c        |  12 +--
 builtin/receive-pack.c |  13 ++-
 builtin/reflog.c       |  85 ++++++++---------
 builtin/replace.c      |  10 +-
 builtin/tag.c          |  10 +-
 builtin/update-ref.c   |  26 ++---
 fast-import.c          |  22 ++---
 refs.c                 | 251 ++++++++++++++++++++++++++++++++++++++++---------
 refs.h                 |  57 +++++++----
 sequencer.c            |  12 +--
 walker.c               |  10 +-
 13 files changed, 352 insertions(+), 179 deletions(-)
-- 
2.2.0.rc3
Previous: Jonathan NiederNext: Stefan Beller
Message 27 of 31 in “ref-transactions-reflog”
  1. 00/14 ref-transactions-reflogStefan Beller, Nov 18, 2014
  2. 01/14 refs.c: make ref_transaction_create a wrapper for ref_transaction_updateStefan Beller, Nov 18, 2014
  3. 02/14 refs.c: make ref_transaction_delete a wrapper for ref_transaction_updateStefan Beller, Nov 18, 2014
  4. 03/14 refs.c: rename the transaction functionsStefan Beller, Nov 18, 2014
  5. 04/14 refs.c: add a function to append a reflog entry to a fdStefan Beller, Nov 18, 2014
  6. 05/14 refs.c: add a new update_type field to ref_updateStefan Beller, Nov 18, 2014
  7. 06/14 refs.c: add a transaction function to append a reflog entryStefan Beller, Nov 18, 2014
  8. 07/14 refs.c: add a flag to allow reflog updates to truncate the logStefan Beller, Nov 18, 2014
  9. 08/14 refs.c: only write reflog update if msg is non-NULLStefan Beller, Nov 18, 2014
  10. 09/14 refs.c: allow multiple reflog updates during a single transactionStefan Beller, Nov 18, 2014
  11. 10/14 reflog.c: use a reflog transaction when writing during expireStefan Beller, Nov 18, 2014
  12. 11/14 refs.c: rename log_ref_setup to create_reflogStefan Beller, Nov 18, 2014
  13. 12/14 refs.c: Remove unlock_ref/close_ref/commit_ref from the refs apiStefan Beller, Nov 18, 2014
  14. 13/14 refs.c: remove lock_any_ref_for_updateStefan Beller, Nov 18, 2014
  15. 14/14 refs.c: allow deleting refs with a broken sha1Stefan Beller, Nov 18, 2014
  16. Michael HaggertyNov 18, 2014
  17. Ronnie SahlbergNov 18, 2014
  18. Michael HaggertyNov 18, 2014
  19. Junio C HamanoNov 18, 2014
  20. Michael HaggertyNov 18, 2014
  21. Junio C HamanoNov 18, 2014
  22. Stefan BellerNov 19, 2014
  23. Jonathan NiederNov 20, 2014
  24. Junio C HamanoNov 20, 2014
  25. Michael HaggertyNov 20, 2014
  26. Jonathan NiederNov 20, 2014
  27. 0/4 Using transactions for the reflogStefan Beller, Nov 27, 2014
  28. 1/4 refs.c: rename the transaction functionsStefan Beller, Nov 27, 2014
  29. 2/4 refs.c: add a new update_type field to ref_updateStefan Beller, Nov 27, 2014
  30. 3/4 refs.c: add a transaction function to append a reflog entryStefan Beller, Nov 27, 2014
  31. 4/4 reflog.c: use a reflog transaction when writing during expireStefan Beller, Nov 27, 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.