From: Chen BoJun <bojun.cbj@gmail.com>
To: git@vger.kernel.org
Cc: "Bojun Chen" <bojun.cbj@alibaba-inc.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Jiang Xin" <zhiyou.jx@alibaba-inc.com>
Subject: [PATCH v3 0/1] purge temporary data if no command is ready to run
Date: Mon, 7 Feb 2022 15:57:20 +0800 [thread overview]
Message-ID: <cover.1644219248.git.bojun.cbj@alibaba-inc.com> (raw)
In-Reply-To: <pull.1124.git.1642987616372.gitgitgadget@gmail.com>
From: Bojun Chen <bojun.cbj@alibaba-inc.com>
Rewrite log messages to more clearly describe the problem.
Chen Bojun (1):
receive-pack: purge temporary data if no command is ready to run
builtin/receive-pack.c | 9 +++++++++
t/t5516-fetch-push.sh | 8 ++++++++
2 files changed, 17 insertions(+)
Range-diff against v2:
1: 72f49f1792 ! 1: 0b5793d1ea receive-pack: purge temporary data if no command is ready to run
@@ Metadata
## Commit message ##
receive-pack: purge temporary data if no command is ready to run
- When pushing a hidden ref, e.g.:
+ When pushing to "receive-pack", commands may have already been marked
+ with error_string or skip_update before being fed to the "pre-receive"
+ hook. E.g.:
- $ git push origin HEAD:refs/hidden/foo
+ * inconsistent push-options for signed push.
+ * not permited shallow updates.
+ * encounter connectivity issues.
+ * push to hidden references.
- "receive-pack" will reject our request with an error message like this:
+ Take pushing to hidden references as an example.
- ! [remote rejected] HEAD -> refs/hidden/foo (deny updating a hidden ref)
+ In order to reduce the size of reference advertisement for git-push from
+ a client which does not support protocol v2 and push negotiation, the
+ administrator may set certain config variables to hide some references
+ like:
+
+ $ git config --system --add receive.hideRefs refs/merge-requests
+
+ Then, if a user made a push like this:
+
+ $ git push origin HEAD:refs/merge-requests/123/head
+
+ "receive-pack" would reject the request with an error message like this:
+
+ ! [remote rejected] HEAD -> refs/merge-requests/123/head
+ (deny updating a hidden ref)
The remote side ("git-receive-pack") will not create the hidden ref as
expected, but the pack file sent by "git-send-pack" is left inside the
--
2.32.0 (Apple Git-132)
next prev parent reply other threads:[~2022-02-07 8:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 1:26 [PATCH] receive-pack: purge temporary data if no command is ready to run BoJun via GitGitGadget
2022-01-24 15:17 ` Ævar Arnfjörð Bjarmason
2022-01-25 16:34 ` Lertz Chen
2022-01-24 23:32 ` Junio C Hamano
2022-01-25 16:49 ` Bojun Chen
2022-01-25 0:22 ` Jiang Xin
2022-01-29 6:35 ` [PATCH v2] " Chen BoJun
2022-02-01 22:51 ` Junio C Hamano
2022-02-01 23:27 ` Junio C Hamano
2022-02-05 7:17 ` Bojun Chen
2022-02-05 8:04 ` Junio C Hamano
2022-02-07 3:36 ` Jiang Xin
2022-02-07 8:02 ` Bojun Chen
2022-02-04 1:17 ` Junio C Hamano
2022-02-05 7:19 ` Bojun Chen
2022-02-05 8:02 ` Junio C Hamano
2022-02-07 7:57 ` Chen BoJun [this message]
2022-02-07 7:57 ` [PATCH v3 1/1] " Chen BoJun
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=cover.1644219248.git.bojun.cbj@alibaba-inc.com \
--to=bojun.cbj@gmail.com \
--cc=avarab@gmail.com \
--cc=bojun.cbj@alibaba-inc.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.