From: Stefan Beller <sbeller@google.com>
To: git@vger.kernel.org, gitster@pobox.com, mhagger@alum.mit.edu
Cc: Stefan Beller <sbeller@google.com>
Subject: [PATCH v4 0/7] ref-transaction-send-pack
Date: Mon, 17 Nov 2014 18:00:33 -0800 [thread overview]
Message-ID: <1416276040-5303-1-git-send-email-sbeller@google.com> (raw)
Hi,
This series has been posted before[1], but is now rebased on the previous
ref-transaction-rename.
It can also be found at github[2] and googlesource[3]
This series finishes the transaction work to provide atomic pushes.
With this series we can now perform atomic pushes to a repository.
Version 2:
- Reordered the capabilities we send so that agent= remains the last
capability listed.
- Reworded the paragraph for atomic push in git-send-pack.txt
- Dropped the patch for receive.preferatomicpush
Version 3:
- Fix a typo in a commit message.
Version 4:
* As Ronnie announced to change employers soon, he'll have only limited
time to work on git in the near future. As this is a rather large patch
series, he is handing this work over to me. That's why I'm sending the
patches this time.
[1] http://www.spinics.net/lists/git/msg241365.html
[2] https://github.com/stefanbeller/git/tree/ref-transactions-send-pack
[3] https://code-review.googlesource.com/#/q/topic:ref-transaction-sendpack
Thanks,
Stefan
Ronnie Sahlberg (7):
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
refs.c: add an err argument to create_reflog
refs.c: add an err argument to create_symref
Documentation/git-push.txt | 7 +-
Documentation/git-send-pack.txt | 7 +-
Documentation/technical/protocol-capabilities.txt | 12 ++-
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 | 79 +++++++++++++----
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 | 45 ++++++++--
send-pack.h | 1 +
t/t5543-atomic-push.sh | 101 ++++++++++++++++++++++
transport.c | 5 ++
transport.h | 1 +
22 files changed, 358 insertions(+), 100 deletions(-)
create mode 100755 t/t5543-atomic-push.sh
--
2.2.0.rc2.5.gf7b9fb2
next reply other threads:[~2014-11-18 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 2:00 Stefan Beller [this message]
2014-11-18 2:00 ` [PATCH v4 1/7] receive-pack.c: add protocol support to negotiate atomic-push Stefan Beller
2014-11-18 2:00 ` [PATCH v4 2/7] send-pack.c: add an --atomic-push command line argument Stefan Beller
2014-11-18 2:00 ` [PATCH v4 3/7] receive-pack.c: use a single transaction when atomic-push is negotiated Stefan Beller
2014-11-18 2:00 ` [PATCH v4 4/7] push.c: add an --atomic-push argument Stefan Beller
2014-11-18 2:00 ` [PATCH v4 5/7] t5543-atomic-push.sh: add basic tests for atomic pushes Stefan Beller
2014-11-18 2:00 ` [PATCH v4 6/7] refs.c: add an err argument to create_reflog Stefan Beller
2014-11-18 2:00 ` [PATCH v4 7/7] refs.c: add an err argument to create_symref Stefan Beller
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=1416276040-5303-1-git-send-email-sbeller@google.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mhagger@alum.mit.edu \
/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).