From: Ronnie Sahlberg <sahlberg@google.com>
To: git@vger.kernel.org
Cc: Ronnie Sahlberg <sahlberg@google.com>
Subject: [PATCH 0/5] ref-transactions-send-pack
Date: Tue, 19 Aug 2014 09:24:46 -0700 [thread overview]
Message-ID: <1408465491-25488-1-git-send-email-sahlberg@google.com> (raw)
List,
This small patch series adds atomic-push support for pushes.
By default git will use the old style non-atomic updates for pushes,
as not to cause disruption in client scripts that may depend on that
behaviour.
Command line arguments are introduced to allow the client side to request/
negotiate atomic pushes if the remote repo supports it.
There is also a new configuration variable where a repo can set that it
wants all pushes to become atomic whether the client requests it or not.
This patch series is called ref-transactions-send-pack and depends on/is built
ontop of the series called ref-transactions-req-strbuf-err
Ronnie Sahlberg (5):
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
receive-pack.c: add receive.atomicpush configuration option
push.c: add an --atomic-push argument
Documentation/config.txt | 5 ++
Documentation/git-push.txt | 7 ++-
Documentation/git-send-pack.txt | 7 ++-
Documentation/technical/protocol-capabilities.txt | 7 +++
builtin/push.c | 2 +
builtin/receive-pack.c | 66 ++++++++++++++++++-----
builtin/send-pack.c | 6 ++-
send-pack.c | 18 +++++--
send-pack.h | 1 +
transport.c | 1 +
transport.h | 1 +
11 files changed, 103 insertions(+), 18 deletions(-)
--
2.0.1.556.ge8f7cba.dirty
next reply other threads:[~2014-08-19 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 16:24 Ronnie Sahlberg [this message]
2014-08-19 16:24 ` [PATCH 1/5] receive-pack.c: add protocol support to negotiate atomic-push Ronnie Sahlberg
2014-08-19 16:24 ` [PATCH 2/5] send-pack.c: add an --atomic-push command line argument Ronnie Sahlberg
2014-08-19 16:24 ` [PATCH 3/5] receive-pack.c: use a single transaction when atomic-push is negotiated Ronnie Sahlberg
2014-08-19 16:24 ` [PATCH 4/5] receive-pack.c: add receive.atomicpush configuration option Ronnie Sahlberg
2014-08-19 16:24 ` [PATCH 5/5] push.c: add an --atomic-push argument Ronnie Sahlberg
-- strict thread matches above, loose matches on Subject: below --
2014-07-31 21:39 [PATCH 0/5] ref-transactions-send-pack Ronnie Sahlberg
2014-08-08 16:15 ` 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=1408465491-25488-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).