From: Taylor Blau <me@ttaylorr.com>
To: Cameron Steffen <cam.steffen94@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git revert --continue --no-verify
Date: Tue, 3 Aug 2021 16:50:45 -0400 [thread overview]
Message-ID: <YQmsJUe6hAMy/QGA@nand.local> (raw)
In-Reply-To: <CAAVFnNkW6Bc4bBDeea2v-VFydvEC0dBw+QXVA0-6OnmF8km3ZA@mail.gmail.com>
Hi Cameron,
On Tue, Aug 03, 2021 at 02:17:07PM -0500, Cameron Steffen wrote:
> Today I tried to run this command and I just got a help screen. I am
> using 2.32.0.
>
> git revert --continue --no-verify
I can't think of any sequencer commands that support a `--[no-]verify`
argument. Did you mistake `--no-verify` for something else, like
`--no-edit` or `--no-commit`?
Thanks,
Taylor
next prev parent reply other threads:[~2021-08-03 20:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 19:17 git revert --continue --no-verify Cameron Steffen
2021-08-03 20:50 ` Taylor Blau [this message]
2021-08-03 20:56 ` Cameron Steffen
2021-08-03 20:59 ` Taylor Blau
2021-08-03 21:33 ` Cameron Steffen
2021-08-03 22:07 ` Taylor Blau
2021-08-04 0:38 ` Junio C Hamano
2021-08-04 18:14 ` Phillip Wood
2021-08-05 1:40 ` Taylor Blau
2021-08-05 1:56 ` Cameron Steffen
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=YQmsJUe6hAMy/QGA@nand.local \
--to=me@ttaylorr.com \
--cc=cam.steffen94@gmail.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).