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

Re: Fwd: git-daemon access-hook race condition

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 12, 2013, 19:15 UTC
Message-ID
<xmqq4n9pq2av.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CAPZPVFbJqbRGQZ+m3-EfahcYegPvVcS-jNTsCXxBqWUsLqyHkg@mail.gmail.com>
Eugene Sajine <euguess@gmail.com> writes:
> Is it possible to have access-hook to be executed after receive?

The whole point of access-hook is to allow it to decide whether the access is allowed or not, so that is a non-starter.

A notification _after_ successful push update is usually done via the post-receive hook in the receiving repository, I think.

Previous: Eugene SajineNext: Eugene Sajine
Message 2 of 10 in “Fwd: git-daemon access-hook race condition”
  1. Eugene SajineSep 12, 2013
  2. Junio C HamanoSep 12, 2013
  3. Fwd: Fwd: git-daemon access-hook race conditionEugene Sajine, Sep 12, 2013
  4. Junio C HamanoSep 12, 2013
  5. Eugene SajineSep 12, 2013
  6. Eugene SajineSep 12, 2013
  7. Eugene SajineSep 13, 2013
  8. Junio C HamanoSep 12, 2013
  9. Eugene SajineSep 12, 2013
  10. Junio C HamanoSep 12, 2013

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.