From: Michael S. Tsirkin <mst@redhat.com>
Date: Wed, 22 May 2013 12:17:14 GMT
Subject: Re: [PATCH] push: document --no-verify
Message-ID: <20130522121714.GB7707@redhat.com>
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