All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] am: Allow passing --no-verify flag
Date: Fri, 18 Nov 2022 13:21:55 -0500	[thread overview]
Message-ID: <Y3fNQ9ysAeOsyOSQ@nand.local> (raw)
In-Reply-To: <20221118132743.3525725-1-thierry.reding@gmail.com>

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.

Thanks,
Taylor

  reply	other threads:[~2022-11-18 18:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 13:27 [PATCH] am: Allow passing --no-verify flag Thierry Reding
2022-11-18 18:21 ` Taylor Blau [this message]
2022-11-19  0:49   ` Thierry Reding

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y3fNQ9ysAeOsyOSQ@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.