From: Ronnie Sahlberg <sahlberg@google.com>
To: git@vger.kernel.org
Cc: Ronnie Sahlberg <sahlberg@google.com>
Subject: [PATCH 0/8] ref-transaction-send-pack
Date: Tue, 21 Oct 2014 13:46:32 -0700 [thread overview]
Message-ID: <1413924400-15418-1-git-send-email-sahlberg@google.com> (raw)
List,
This series has been posted before but is now rebased on the previous
ref-transaction-rename series that are against next.
This series can also be found at :
https://github.com/rsahlberg/git/tree/ref-transactions-send-pack
This series finishes the transaction work to provide atomic pushes.
With this series we can now perform atomic pushes to a repository.
Ronnie Sahlberg (8):
receive-pack.c: add protocol support to negotiate atomic-push
send-pack.c: add an --atomic-push command line argument
receive-pack.c: use a single transaction when atomic-push is
negotiated
push.c: add an --atomic-push argument
t5543-atomic-push.sh: add basic tests for atomic pushes
receive-pack.c: add a receive.preferatomicpush configuration variable
refs.c: add an err argument to create_reflog
refs.c: add an err argument to create_symref
Documentation/config.txt | 4 +
Documentation/git-push.txt | 7 +-
Documentation/git-send-pack.txt | 7 +-
Documentation/technical/protocol-capabilities.txt | 19 +++-
builtin/branch.c | 7 +-
builtin/checkout.c | 21 +++-
builtin/clone.c | 15 ++-
builtin/init-db.c | 8 +-
builtin/notes.c | 7 +-
builtin/push.c | 2 +
builtin/receive-pack.c | 87 +++++++++++---
builtin/remote.c | 26 +++--
builtin/send-pack.c | 6 +-
builtin/symbolic-ref.c | 6 +-
cache.h | 1 -
refs.c | 93 ++++++++-------
refs.h | 5 +-
remote.h | 3 +-
send-pack.c | 47 +++++++-
send-pack.h | 1 +
t/t5543-atomic-push.sh | 133 ++++++++++++++++++++++
transport.c | 5 +
transport.h | 1 +
23 files changed, 411 insertions(+), 100 deletions(-)
create mode 100755 t/t5543-atomic-push.sh
--
2.1.0.rc2.206.gedb03e5
next reply other threads:[~2014-10-21 20:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 20:46 Ronnie Sahlberg [this message]
2014-10-21 20:46 ` [PATCH 1/8] receive-pack.c: add protocol support to negotiate atomic-push Ronnie Sahlberg
2014-10-30 19:59 ` Junio C Hamano
2014-10-30 20:46 ` Ronnie Sahlberg
2014-10-21 20:46 ` [PATCH 2/8] send-pack.c: add an --atomic-push command line argument Ronnie Sahlberg
2014-10-30 20:04 ` Junio C Hamano
2014-10-30 21:21 ` Ronnie Sahlberg
2014-10-21 20:46 ` [PATCH 3/8] receive-pack.c: use a single transaction when atomic-push is negotiated Ronnie Sahlberg
2014-10-30 20:05 ` Junio C Hamano
2014-10-21 20:46 ` [PATCH 4/8] push.c: add an --atomic-push argument Ronnie Sahlberg
2014-10-21 20:46 ` [PATCH 5/8] t5543-atomic-push.sh: add basic tests for atomic pushes Ronnie Sahlberg
2014-10-21 20:46 ` [PATCH 6/8] receive-pack.c: add a receive.preferatomicpush configuration variable Ronnie Sahlberg
2014-10-30 20:11 ` Junio C Hamano
2014-10-30 21:36 ` Ronnie Sahlberg
2014-10-30 22:03 ` Junio C Hamano
2014-10-30 22:26 ` Ronnie Sahlberg
2014-10-21 20:46 ` [PATCH 7/8] refs.c: add an err argument to create_reflog Ronnie Sahlberg
2014-10-21 20:46 ` [PATCH 8/8] refs.c: add an err argument to create_symref 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=1413924400-15418-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).