From: "Michael S. Tsirkin" <mst@redhat.com>
To: Thomas Rast <trast@inf.ethz.ch>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Aaron Schrab <aaron@schrab.com>
Subject: Re: [PATCH] push: document --no-verify
Date: Wed, 22 May 2013 15:17:14 +0300 [thread overview]
Message-ID: <20130522121714.GB7707@redhat.com> (raw)
In-Reply-To: <878v378b8a.fsf@linux-k42r.v.cablecom.net>
On Wed, May 22, 2013 at 02:12:21PM +0200, Thomas Rast wrote:
> "Michael S. Tsirkin" <mst@redhat.com> writes:
>
> > commit ec55559f937727bcb0fa8a3dfe6af68c188e968a added
> > --no-verify flag to git push, but didn't document it.
> > It's a useful flag when using pre-push hooks so
> > add the documentation.
> >
> > Suggested-by: Thomas Rast <trast@inf.ethz.ch>
> > Cc: Aaron Schrab <aaron@schrab.com>
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> [...]
> > +-n::
> > +--no-verify::
> > + This option bypasses the pre-commit and commit-msg hooks.
> > + See also linkgit:githooks[5].
> > +
>
> Umm, half of that is not correct :-)
>
> Push doesn't have the -n short form that git-commit does,
Hmm true - in fact -n means dry-run.
> and the hook
> names are wrong.
>
> I also ended up writing a patch myself; sorry for not telling you on
> IRC:
>
> http://thread.gmane.org/gmane.comp.version-control.git/225141
Great, thanks.
> --
> Thomas Rast
> trast@{inf,student}.ethz.ch
prev parent reply other threads:[~2013-05-22 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 10:43 [PATCH] push: document --no-verify Michael S. Tsirkin
2013-05-22 12:12 ` Thomas Rast
2013-05-22 12:17 ` Michael S. Tsirkin [this message]
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=20130522121714.GB7707@redhat.com \
--to=mst@redhat.com \
--cc=aaron@schrab.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=trast@inf.ethz.ch \
/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.