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

thoughts on a possible "pre-upload" hook

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Sep 22, 2009, 10:20 UTC
Message-ID
<2e24e5b90909220320rbd5fd1l40c7898656445232@mail.gmail.com>
Hello,

As git is used more and more in corporate-type environments, at some point it becomes convenient to have *branches* (or more accurately, refs) that are not readable. The simplest way to do this (from git's point of view) is to allow a "pre-upload" hook, rather like the "pre-receive" hook or "update" hook.

I don't know the upload pack protocol enough to know whether this is a stupid idea or not; please tell me if so :-) But things that were seemingly "impossible" in the early days are being talked about now and even being implemented so I felt brave enough to ask.

I'm afraid my C programming days are long gone, but if anything can be done in shell or perl, with a little git.guidance, I'll do whatever I can.

-- 
Sitaram
Next: Randal L. Schwartz
Message 1 of 9 in “thoughts on a possible "pre-upload" hook”
  1. Sitaram ChamartySep 22, 2009
  2. Randal L. SchwartzSep 22, 2009
  3. Matthieu MoySep 22, 2009
  4. Shawn O. PearceSep 22, 2009
  5. Sitaram ChamartySep 25, 2009
  6. Matthieu MoySep 25, 2009
  7. Sitaram ChamartySep 25, 2009
  8. Adam BrewsterSep 28, 2009
  9. Sitaram ChamartySep 28, 2009

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.