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

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

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Sep 25, 2009, 12:29 UTC
Message-ID
<vpqab0j1a2s.fsf@bauges.imag.fr>
In-Reply-To
<2e24e5b90909250454s7ed35b9ch10b954b0b1a40cfe@mail.gmail.com>
Sitaram Chamarty <sitaramc@gmail.com> writes:
> yes indeed -- if someone were to foolishly merge a "secret" branch
> into a "normal" branch, so that it is now reachable from a "normal"
> branch, that's his problem -- that cannot be within the scope of this
> check.

Merging is not the only scenario. Adding a tag could make secret things become visible too. I'm not saying the approach isn't viable, but if it gets implemented, it should be done with care to make sure there's no easy mis-use that would lead to reveal a secret (typically, I'd do that with a whitelist and not a black-list, so that new references are secret by default).

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Sitaram ChamartyNext: Sitaram Chamarty
Message 6 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.