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

Re: hook for rebase --continue

From
MFMartin Fick <mfick@codeaurora.org>
Date
Nov 7, 2011, 19:46 UTC
Message-ID
<201111071246.35100.mfick@codeaurora.org>
In-Reply-To
<CALts4TQ545L1d1J0EiUjd7x=WBJpjCCv6UsXZOoGQAC29RqC5g@mail.gmail.com>
On Monday, November 07, 2011 12:42:32 pm Matt Graham wrote:
> Does anyone else share my expectation that the pre-commit
> hook should run during a rebase? Or at least for the
> first commit following a rebase conflict?

I have had the same concern. We use a change-id hook for Gerrit development, and it adds a footer line to commit messages. If during a rebase, it is accidentally removed, the hook does not get run and does not re-add it,

-Martin
-- 
Employee of Qualcomm Innovation Center, Inc. which is a 
member of Code Aurora Forum
Previous: Matt GrahamNext: Neal Kreitzinger
Message 2 of 5 in “hook for rebase --continue”
  1. Matt GrahamNov 7, 2011
  2. Martin FickNov 7, 2011
  3. Neal KreitzingerNov 10, 2011
  4. Neal KreitzingerNov 10, 2011
  5. Neal KreitzingerNov 15, 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.