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

Re: [PATCH 2/3] Only show log entries for new revisions in hooks--update

From
Junio C Hamano <junkio@cox.net>
Date
Feb 13, 2007, 17:41 UTC
Message-ID
<7vbqjyymye.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<200702131424.06983.andyparkins@gmail.com>

I seem to recall that something like this was discussed recently on the list.

While excluding commits on already updated branches works if the same set of recipients receive e-mails for both branches by eliminating the duplicates, I suspect that in more elaborate settings people would want to do different notices for different branches, and for that kind of usage people who subscribes only to branch1 in your picture would miss what happened on branch2.

Or maybe branch1 is the main integration branch (e.g. 'master', 'next') while branch2 is a tentative topic that does not send out notification e-mails.

If we want to take this example hook seriously, I suspect that the existing mechanism based on hooks.* variables might need to be made to allow finer grained, per-branch, control. I dunno.

Post 1.5.0.
Previous: Andy ParkinsNext: Andy Parkins
Message 2 of 3 in “Only show log entries for new revisions in hooks--update”
  1. 2/3 Only show log entries for new revisions in hooks--updateAndy Parkins, Feb 13, 2007
  2. Junio C HamanoFeb 13, 2007
  3. Andy ParkinsFeb 13, 2007

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.