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

Re: git-http-push and hooks

From
Junio C Hamano <junkio@cox.net>
Date
Feb 7, 2006, 21:17 UTC
Message-ID
<7vwtg6uaw6.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20060207202351.GA3833@reactrix.com>
Nick Hengeveld <nickh@reactrix.com> writes:
Show 5 quoted lines
> There are options for a DAV-only environment though.  While the hooks
> themselves can't be run, git-http-push can be modified to update the
> remote pack and ref info (although it's not clear to me under what
> conditions it should do so...)  DAV-specific versions of pack
> management utilities are feasible as well.

If the server info updates is the _only_ problem, then perhaps that would be the easiest and cleanest. Whenever you update or add a ref you would need to update info/refs (otherwise ls-remote would not give you the latest info), and whenever you repack you would need to update objects/info/packs.

You may probably want to have a CGI to allow you manage the repository remotely anyway, to trigger a repack or remove a stale branch head, for example. Once you go that route maybe having the CGI to do something like the pack protocol for more efficient transfer might become more attractive.

Previous: Junio C HamanoNext: Nick Hengeveld
Message 8 of 12 in “git-http-push and hooks”
  1. Bertrand Jacquin (Beber)Feb 6, 2006
  2. Nick HengeveldFeb 6, 2006
  3. Fredrik KuivinenFeb 7, 2006
  4. Nick HengeveldFeb 7, 2006
  5. Fredrik KuivinenFeb 7, 2006
  6. Bertrand JacquinFeb 7, 2006
  7. Junio C HamanoFeb 7, 2006
  8. Junio C HamanoFeb 7, 2006
  9. Nick HengeveldFeb 7, 2006
  10. Junio C HamanoFeb 7, 2006
  11. Nick HengeveldFeb 7, 2006
  12. Bertrand JacquinFeb 7, 2006

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.