From: Pat Notz Date: Sun, 22 Mar 2009 16:56:04 GMT Subject: Re: [PATCH] githooks documentation: post-checkout hook is also called after clone Message-ID: <1cd1989b0903220956w47ca2521s8945a4c71225909c@mail.gmail.com> In-Reply-To: <49C66B03.6020908@web.de> On Sun, Mar 22, 2009 at 10:44 AM, Jens Lehmann wrote: > The documentation of the post-checkout hook just talks > about git-checkout. But recently git-clone was changed to > call it too, so we have to document that in githooks.txt. > > Signed-off-by: Jens Lehmann > --- >  Documentation/githooks.txt |    3 +++ >  1 files changed, 3 insertions(+), 0 deletions(-) > > diff --git a/Documentation/githooks.txt b/Documentation/githooks.txt > index 1fd512b..76deefc 100644 > --- a/Documentation/githooks.txt > +++ b/Documentation/githooks.txt > @@ -151,6 +151,9 @@ indicating whether the checkout was a branch checkout (changing branches, >  flag=1) or a file checkout (retrieving a file from the index, flag=0). >  This hook cannot affect the outcome of 'git-checkout'. > > +It is also run after 'git-clone'. The first parameter given to the hook is > +the null-ref, the second the ref of the new HEAD and the flag is always 1. > + I don't think that's true if you clone with the --no-checkout (-n) option though. >  This hook can be used to perform repository validity checks, auto-display >  differences from the previous HEAD if different, or set working dir metadata >  properties. > -- > 1.6.2.1.275.ga797b > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at  http://vger.kernel.org/majordomo-info.html >