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

Re: [RFC] Automagic patch merge ack emails

From
Richard Hartmann <richih.mailinglist@gmail.com>
Date
Dec 23, 2008, 14:46 UTC
Message-ID
<2d460de70812230646r181f59d0y55055e96ad6eda84@mail.gmail.com>
In-Reply-To
<7v8wq8hs34.fsf@gitster.siamese.dyndns.org>
On Mon, Dec 22, 2008 at 21:29, Junio C Hamano <gitster@pobox.com> wrote:
Show 8 quoted lines
> The only time that it may make a difference to you is when things are
> pushed out to the public repository, and there is a mechanism for
> automating tasks after new commits hits the public repository: the
> post-receive hook.  contrib/hooks/post-receive-email may be a good example
> to study if you are interested (I use it in my day job repository, but I
> do not use the hook in git.git because the style of announcing I adopted
> on this list is to send out "What's in/cooking" messages once or twice a
> week).

That's pretty much what I meant, yes. As to the rest, I am still thinking too much in VCS, not DVCS, style, I guess. Thanks for your clarification, it all makes sense, now :)

Richard
Previous: Junio C HamanoNext: Boyd Stephen Smith Jr.
Message 3 of 4 in “[RFC] Automagic patch merge ack emails”
  1. Richard HartmannDec 22, 2008
  2. Junio C HamanoDec 22, 2008
  3. Richard HartmannDec 23, 2008
  4. Boyd Stephen Smith Jr.Dec 22, 2008

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.