git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git smart http: parsing commit messages in git-receive-pack

From
Junio C Hamano <gitster@pobox.com>
Date
May 8, 2017, 02:08 UTC
Message-ID
<xmqq4lwwayn4.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CAGyf7-EDHPdL_YvNoC9QNy11=YfxSpmZBFZ5UR50ub1o2yqAug@mail.gmail.com>
Bryan Turner <bturner@atlassian.com> writes:
> That means if you pair a pre-receive hook with Git 2.11 or newer on
> the server, you should be able to achieve what you're looking for.

It probably is worth mentioning that even without the "quarantine" changes of 2.11, the new objects brought in by a rejected push cannot be used because they are not reachable from any ref, and will be discarded as garbage when the next GC run. So pre-receive should be sufficient for the purpose of "not accepting" an undesirable push, with older versions of Git. You can view the "quarantine" feature mostly as "quality of implementation" issue.

Previous: Bryan Turner
Message 3 of 3 in “Git smart http: parsing commit messages in git-receive-pack”
  1. akos tajtiMay 6, 2017
  2. Bryan TurnerMay 6, 2017
  3. Junio C HamanoMay 8, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.