From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Petr Baudis <pasky@suse.cz>, Josh England <jjengla@sandia.gov>
Subject: Re: cloning/pulling hooks
Date: Wed, 29 Aug 2007 15:28:30 +0100 [thread overview]
Message-ID: <200708291528.31599.andyparkins@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708291421060.28586@racer.site>
On Wednesday 2007 August 29, Johannes Schindelin wrote:
> > 1) Start a new project
> > 2) Install a pre-commit hook that checks that every patch meets some
> > arbitrary coding standard
> > 3) Clone to laptop
> > 4) Kick self the first time you make a commit that doesn't adhere to
> > coding standards that would have been enforced by the hook script.
>
> For me it is
>
> 4) put the check into the Makefile where it belongs.
I suppose you are right, the reason I pick the hook is because I don't mind
having untidy code in the working tree but don't want it in the repository.
Also, it was given as an example hook so I enabled it :-)
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-08-29 14:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1188319608.6106.63.camel@beauty>
[not found] ` <20070828172709.GB1219@pasky.or.cz>
2007-08-29 9:05 ` cloning/pulling hooks Andy Parkins
2007-08-29 9:52 ` Petr Baudis
2007-08-29 12:56 ` Andy Parkins
2007-08-29 13:21 ` Johannes Schindelin
2007-08-29 14:28 ` Andy Parkins [this message]
2007-08-29 20:27 ` Alex Riesen
2007-08-29 13:18 ` Benjamin Collins
2007-08-29 13:39 ` Petr Baudis
2007-08-29 13:49 ` Johannes Schindelin
2007-08-29 13:54 ` Petr Baudis
2007-08-29 14:06 ` Johannes Schindelin
2007-08-29 14:19 ` Petr Baudis
2007-08-29 14:31 ` Johannes Schindelin
2007-08-29 14:41 ` Petr Baudis
2007-08-29 14:56 ` Johannes Schindelin
2007-08-29 20:35 ` Alex Riesen
2007-08-29 19:45 ` Junio C Hamano
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=200708291528.31599.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jjengla@sandia.gov \
--cc=pasky@suse.cz \
/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.