diff options
author | Emily Shaffer <emilyshaffer@google.com> | 2019-07-11 14:19:19 -0700 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2019-07-12 09:24:10 -0700 |
commit | 3bca1e7f9f9708b970035a641d21f8c5cec1cd88 (patch) | |
tree | dfc12425711865fdbf6e599ac696deb3ad289bea /t/t3303-notes-subtrees.sh | |
parent | Git 2.22 (diff) | |
download | tgif-3bca1e7f9f9708b970035a641d21f8c5cec1cd88.tar.xz |
transport-helper: enforce atomic in push_refs_with_push
Teach transport-helper how to notice if skipping a ref during push would
violate atomicity on the client side. We notice that a ref would be
rejected, and choose not to send it, but don't notice that if the client
has asked for --atomic we are violating atomicity if all the other
pushes we are sending would succeed. Asking the server end to uphold
atomicity wouldn't work here as the server doesn't have any idea that we
tried to update a ref that's broken.
The added test-case is a succinct way to reproduce this issue that fails
today. The same steps work fine when we aren't using a transport-helper
to get to the upstream, i.e. when we've added a local repository as a
remote:
git remote add ~/upstream upstream
Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t3303-notes-subtrees.sh')
0 files changed, 0 insertions, 0 deletions