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

Re: [PATCH] am: Allow passing --no-verify flag

From
TRThierry Reding <thierry.reding@gmail.com>
Date
Nov 19, 2022, 00:49 UTC
Message-ID
<Y3goBHxEd8xUE4Bc@orome>
In-Reply-To
<Y3fNQ9ysAeOsyOSQ@nand.local>
On Fri, Nov 18, 2022 at 01:21:55PM -0500, Taylor Blau wrote:
Show 10 quoted lines
> On Fri, Nov 18, 2022 at 02:27:43PM +0100, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > The git-am --no-verify flag is analogous to the same flag passed to
> > git-commit. It bypasses the pre-applypatch and applypatch-msg hooks
> > if they are enabled.
> 
> The patch below looks reasonable to me. Is there a way that we could
> test this easily? It looks trivially correct to my eyes, but I want to
> avoid the possibility of regressing here in the future.

Yeah, turns out this can be pretty easily checked. I'll resend a v2 with the test included.

Thierry
Previous: Taylor Blau
Message 3 of 3 in “am: Allow passing --no-verify flag”
  1. am: Allow passing --no-verify flagThierry Reding, Nov 18, 2022
  2. Taylor BlauNov 18, 2022
  3. Thierry RedingNov 19, 2022

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.