From: Stefan Beller <sbeller@google.com>
To: git@vger.kernel.org, mhagger@alum.mit.edu, jrnieder@gmail.com,
ronniesahlberg@gmail.com, gitster@pobox.com
Cc: Stefan Beller <sbeller@google.com>
Subject: [PATCH 0/8] Making reflog modifications part of the transactions API
Date: Fri, 5 Dec 2014 18:46:27 -0800 [thread overview]
Message-ID: <1417833995-25687-1-git-send-email-sbeller@google.com> (raw)
This goes on top of Michaels series. The idea of this series is make the
reflogs being part of the transaction API, so it will be part of the contract
of transaction_commit to either commit all the changes or none at all.
Currently when using the transaction API to change refs, also reflogs are changed.
But the changes to the reflogs just happen as a side effect and not as part of
the atomic part of changes we want to commit altogether.
Ronnie Sahlberg (3):
refs.c: use a reflog transaction when writing during expire
refs.c: rename log_ref_setup to create_reflog
refs.c: allow deleting refs with a broken sha1
Stefan Beller (5):
refs.c: let fprintf handle the formatting
refs.c: rename the transaction functions
refs.c: rename transaction.updates to transaction.ref_updates
refs.c: add transaction function to append to the reflog
refs.c: add transaction function to delete the reflog
branch.c | 13 +-
builtin/branch.c | 5 +-
builtin/checkout.c | 8 +-
builtin/commit.c | 10 +-
builtin/fetch.c | 12 +-
builtin/receive-pack.c | 13 +-
builtin/replace.c | 10 +-
builtin/tag.c | 10 +-
builtin/update-ref.c | 26 ++--
cache.h | 7 +
fast-import.c | 22 +--
refs.c | 359 ++++++++++++++++++++++++++++++++++---------------
refs.h | 43 +++---
sequencer.c | 12 +-
t/t3200-branch.sh | 8 ++
walker.c | 10 +-
16 files changed, 359 insertions(+), 209 deletions(-)
--
2.2.0
next reply other threads:[~2014-12-06 2:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 2:46 Stefan Beller [this message]
2014-12-06 2:46 ` [PATCH 1/8] refs.c: let fprintf handle the formatting Stefan Beller
2014-12-06 2:46 ` [PATCH 2/8] refs.c: rename the transaction functions Stefan Beller
2014-12-11 21:42 ` Junio C Hamano
2014-12-11 21:48 ` Stefan Beller
2014-12-06 2:46 ` [PATCH 3/8] refs.c: rename transaction.updates to transaction.ref_updates Stefan Beller
2014-12-06 2:46 ` [PATCH 4/8] refs.c: add transaction function to append to the reflog Stefan Beller
2014-12-11 21:50 ` Junio C Hamano
2014-12-06 2:46 ` [PATCH 5/8] refs.c: add transaction function to delete " Stefan Beller
2014-12-06 2:46 ` [PATCH 6/8] refs.c: use a reflog transaction when writing during expire Stefan Beller
2014-12-06 2:46 ` [PATCH 7/8] refs.c: rename log_ref_setup to create_reflog Stefan Beller
2014-12-06 2:46 ` [PATCH 8/8] refs.c: allow deleting refs with a broken sha1 Stefan Beller
2014-12-08 20:05 ` [PATCH 0/8] Making reflog modifications part of the transactions API Stefan Beller
2014-12-08 21:54 ` Jonathan Nieder
2014-12-12 16:17 ` Michael Haggerty
2014-12-12 20:51 ` Stefan Beller
2014-12-12 21:16 ` ronnie sahlberg
2014-12-14 23:17 ` 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=1417833995-25687-1-git-send-email-sbeller@google.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=mhagger@alum.mit.edu \
--cc=ronniesahlberg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).