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

Re: (Ab)using filter-branch from a post-receive hook

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 15, 2012, 06:44 UTC
Message-ID
<7va9z15xrc.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CEAB8F11-05A4-46B4-A0B5-B51B14EAD536@wincent.com>
Wincent Colaiuta <win@wincent.com> writes:
Show 9 quoted lines
> On Jul 14, 2012, at 10:25 PM, Junio C Hamano wrote:
>
>> I did not see anything wrong doing what you described in the
>> post-receive, even though having the hook in the "scratch" felt
>> strange, as the "copying from authoritative" would also want to be
>> automated and the natural triggering mechanism to do so would be a
>> post-receive there.  What issues were you worried about?
>
> The part that I left out, to keep things simple, is that ...

I said "strange", not "wrong". If it is undesirable to hook the "authoritative" repository, it is perfectly fine to hook on the receiving end.

So what issues were you worried about?
Previous: Wincent ColaiutaNext: Wincent Colaiuta
Message 4 of 5 in “(Ab)using filter-branch from a post-receive hook”
  1. Wincent ColaiutaJul 15, 2012
  2. Junio C HamanoJul 15, 2012
  3. Wincent ColaiutaJul 15, 2012
  4. Junio C HamanoJul 15, 2012
  5. Wincent ColaiutaJul 15, 2012

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.