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

Re: thoughts on a possible "pre-upload" hook

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Sep 28, 2009, 03:02 UTC
Message-ID
<2e24e5b90909272002r53b0a82dw9cb52bdc7bbd477@mail.gmail.com>
In-Reply-To
<c376da900909271901q1667ecacw730ba5180a558f3b@mail.gmail.com>
On Mon, Sep 28, 2009 at 7:31 AM, Adam Brewster <adambrewster@gmail.com> wrote:
Show 8 quoted lines
>> 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.
>>
>
> What's the benefit of this over using multiple repositories?

Over a long pm chat over irc with Ilari, I have come to the same conclusion. I was hoping there would be some administrative convenience or workflow convenience to doing this, but whether there is or not is debatable, and even if there is, there are enough failure modes to make this have a lot of caveats.

-- 
Sitaram
Previous: Adam Brewster
Message 9 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.