git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ronnie Sahlberg <sahlberg@google.com>
To: git@vger.kernel.org
Cc: Ronnie Sahlberg <sahlberg@google.com>
Subject: [PATCH 00/11] Add transaction support for reflog
Date: Wed,  4 Jun 2014 11:57:41 -0700	[thread overview]
Message-ID: <1401908272-7600-1-git-send-email-sahlberg@google.com> (raw)

This patch series is based on the ref-transaction series and is available at
https://github.com/rsahlberg/git/tree/ref-transactions-reflog

This patch series adds transaction support for updating the reflog.

Ronnie Sahlberg (11):
  refs.c make ref_transaction_create a wrapper to ref_transaction_update
  refs.c: make ref_transaction_delete a wrapper for
    ref_transaction_update
  refs.c: rename the transaction functions
  refs.c: add a new update_type field to ref_update
  refs.c: add a function to append a reflog entry to a fd
  lockfile.c: make hold_lock_file_for_append preserve meaningful errno
  refs.c: add a transaction function to append a reflog entry
  refs.c: add a flag to allow reflog updates to truncate the log
  refs.c: only write reflog update if msg is non-NULL
  refs.c: allow multiple reflog updates during a single transaction
  reflog.c: use a reflog transaction when writing during expire

 branch.c               |  11 +-
 builtin/commit.c       |  14 +--
 builtin/fetch.c        |  12 +-
 builtin/receive-pack.c |  14 +--
 builtin/reflog.c       |  84 ++++++-------
 builtin/replace.c      |  10 +-
 builtin/tag.c          |  10 +-
 builtin/update-ref.c   |  22 ++--
 copy.c                 |  20 ++--
 fast-import.c          |  23 ++--
 lockfile.c             |   7 +-
 refs.c                 | 317 ++++++++++++++++++++++++++++++++++++-------------
 refs.h                 |  64 ++++++----
 sequencer.c            |  12 +-
 walker.c               |  17 ++-
 15 files changed, 404 insertions(+), 233 deletions(-)

-- 
2.0.0.578.gb9e379f

             reply	other threads:[~2014-06-04 18:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 18:57 Ronnie Sahlberg [this message]
2014-06-04 18:57 ` [PATCH 01/11] refs.c make ref_transaction_create a wrapper to ref_transaction_update Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 02/11] refs.c: make ref_transaction_delete a wrapper for ref_transaction_update Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 03/11] refs.c: rename the transaction functions Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 04/11] refs.c: add a new update_type field to ref_update Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 05/11] refs.c: add a function to append a reflog entry to a fd Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 06/11] lockfile.c: make hold_lock_file_for_append preserve meaningful errno Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 07/11] refs.c: add a transaction function to append a reflog entry Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 08/11] refs.c: add a flag to allow reflog updates to truncate the log Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 09/11] refs.c: only write reflog update if msg is non-NULL Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 10/11] refs.c: allow multiple reflog updates during a single transaction Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 11/11] reflog.c: use a reflog transaction when writing during expire Ronnie Sahlberg

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=1401908272-7600-1-git-send-email-sahlberg@google.com \
    --to=sahlberg@google.com \
    --cc=git@vger.kernel.org \
    /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).