From: Han Xin <chiyutianyi@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, Git List <git@vger.kernel.org>
Cc: Han Xin <hanxin.hx@alibaba-inc.com>,
Jiang Xin <zhiyou.jx@alibaba-inc.com>
Subject: [PATCH 2/2] send-pack: check atomic push before running GPG
Date: Tue, 15 Sep 2020 17:58:27 +0800 [thread overview]
Message-ID: <20200915095827.52047-2-hanxin.hx@alibaba-inc.com> (raw)
In-Reply-To: <20200915095827.52047-1-hanxin.hx@alibaba-inc.com>
Atomic push may be rejected, which makes it meanigless to generate push
cert first. Therefore, the push cert generation was moved after atomic
check.
Reviewed-by: Jiang Xin <zhiyou.jx@alibaba-inc.com>
Signed-off-by: Han Xin <hanxin.hx@alibaba-inc.com>
---
send-pack.c | 14 +++++++-------
t/t5534-push-signed.sh | 2 +-
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/send-pack.c b/send-pack.c
index d671ab5d05..58416a6f6d 100644
--- a/send-pack.c
+++ b/send-pack.c
@@ -447,13 +447,6 @@ int send_pack(struct send_pack_args *args,
if (ref->deletion && !allow_deleting_refs)
ref->status = REF_STATUS_REJECT_NODELETE;
- if (!args->dry_run)
- advertise_shallow_grafts_buf(&req_buf);
-
- if (!args->dry_run && push_cert_nonce)
- cmds_sent = generate_push_cert(&req_buf, remote_refs, args,
- cap_buf.buf, push_cert_nonce);
-
/*
* Clear the status for each ref and see if we need to send
* the pack data.
@@ -489,6 +482,13 @@ int send_pack(struct send_pack_args *args,
ref->status = REF_STATUS_EXPECTING_REPORT;
}
+ if (!args->dry_run)
+ advertise_shallow_grafts_buf(&req_buf);
+
+ if (!args->dry_run && push_cert_nonce)
+ cmds_sent = generate_push_cert(&req_buf, remote_refs, args,
+ cap_buf.buf, push_cert_nonce);
+
/*
* Finally, tell the other end!
*/
diff --git a/t/t5534-push-signed.sh b/t/t5534-push-signed.sh
index d0fcdc900e..927750a408 100755
--- a/t/t5534-push-signed.sh
+++ b/t/t5534-push-signed.sh
@@ -273,7 +273,7 @@ test_expect_success GPGSM 'fail without key and heed user.signingkey x509' '
test_cmp expect dst/push-cert-status
'
-test_expect_failure GPG 'check atomic push before running GPG' '
+test_expect_success GPG 'check atomic push before running GPG' '
prepare_dst &&
git -C dst config receive.certnonceseed sekrit &&
write_script gpg <<-EOF &&
--
2.28.0
next prev parent reply other threads:[~2020-09-15 9:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 9:58 [PATCH 1/2] t5534: new test case for atomic signed push Han Xin
2020-09-15 9:58 ` Han Xin [this message]
2020-09-15 21:02 ` [PATCH 2/2] send-pack: check atomic push before running GPG Junio C Hamano
2020-09-15 21:40 ` Junio C Hamano
2020-09-16 1:53 ` Jiang Xin
2020-09-16 4:37 ` Junio C Hamano
2020-09-16 11:49 ` Jiang Xin
2020-09-16 23:44 ` Junio C Hamano
2020-09-18 4:50 ` [PATCH v2] send-pack: run GPG after atomic push checking Han Xin
2020-09-19 0:02 ` Junio C Hamano
2020-09-19 14:47 ` [PATCH v3] " Han Xin
2020-09-19 23:02 ` Junio C Hamano
2020-09-20 6:20 ` [PATCH v4] " Han Xin
2020-09-16 17:35 ` [PATCH 2/2] send-pack: check atomic push before running GPG 韩欣(炽天)
2020-09-15 20:31 ` [PATCH 1/2] t5534: new test case for atomic signed push Junio C Hamano
2020-09-16 0:34 ` brian m. carlson
2020-09-15 20:34 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200915095827.52047-2-hanxin.hx@alibaba-inc.com \
--to=chiyutianyi@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hanxin.hx@alibaba-inc.com \
--cc=zhiyou.jx@alibaba-inc.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).