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
APAndy Parkins <andyparkins@gmail.com>
Date
Feb 13, 2007, 18:08 UTC
Message-ID
<200702131808.19291.andyparkins@gmail.com>
In-Reply-To
<7vbqjyymye.fsf@assigned-by-dhcp.cox.net>
On Tuesday 2007, February 13, Junio C Hamano wrote:
Show 5 quoted lines
> 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.

Absolutely - per-branch sounds great. However, as that is definitely a post-1.5.0 topic, I wanted to get the hook that was there in better shape for the release.

Until the per-branch work is done, I think this patch is worth having.
Andy
-- 
Dr Andrew Parkins, M Eng (Hons), AMIEE
andyparkins@gmail.com
Previous: Junio C Hamano
Message 3 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.