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

Re: git merge auto-commit doesn't fire pre-commit hook

From
LCLiam Clarke <liam.clarke-hutchinson@adscale.co.nz>
Date
Feb 17, 2011, 05:05 UTC
Message-ID
<542F1586-F49F-4CD4-A15A-0C7002EB8CE1@adscale.co.nz>
In-Reply-To
<AANLkTim+_s5S46QwhHLquMLsoqCwLASdyeW1Lu6md=TB@mail.gmail.com>
It can't affect the merge, but I could check for the data's existence, rm it, commit the deletion, and then scold the naughty developer... Yeah, not a bad idea actually. :) Cheers Jay.
On 17/02/2011, at 5:52 PM, Jay Soffian wrote:
Show 7 quoted lines
> On Wed, Feb 16, 2011 at 11:44 PM, Liam Clarke
> <liam.clarke-hutchinson@adscale.co.nz> wrote:
>> What about when I'm merging my own feature branches into master? Also, past performance indicates that yelling about bad stuff in merges works quite well when they're in the same office as you...
> 
> BTW, why not just use the post-merge hook to amend the merge after the fact?
> 
> j.
Previous: Jay Soffian
Message 6 of 6 in “git merge auto-commit doesn't fire pre-commit hook”
  1. Liam ClarkeFeb 16, 2011
  2. Jay SoffianFeb 17, 2011
  3. Liam ClarkeFeb 17, 2011
  4. Jay SoffianFeb 17, 2011
  5. Jay SoffianFeb 17, 2011
  6. Liam ClarkeFeb 17, 2011

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.