git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Branchaud <marcnarc@xiplink.com>
To: Chris Packham <judge.packham@gmail.com>
Cc: spearce@spearce.org, git@vger.kernel.org
Subject: Re: [PATCH/RFC] Documentation/git-gc.txt: add reference to githooks
Date: Mon, 28 Jun 2010 14:43:21 -0400	[thread overview]
Message-ID: <4C28ED49.90906@xiplink.com> (raw)
In-Reply-To: <1277744834-7546-1-git-send-email-judge.packham@gmail.com>

How about also adding a templates/hooks--pre-auto-gc.sample file?

		M.


On 10-06-28 01:07 PM, Chris Packham wrote:
> This advertises the existence of the 'pre-auto-gc' hook and adds a cross
> reference to where the hook is documented.
> 
> Signed-off-by: Chris Packham <judge.packham@gmail.com>
> ---
> I had to go fishing in the code to find out about the pre-auto-gc hook. From
> reading the git-gc man page it wasn't obvious to me that there would be a hook
> for 'git gc --auto'. The relevant config variables are mentioned so it seems
> logical to mention the hooks also. The only precedent I found for this was in
> the git-commit man page which has a section listing the hooks that are
> available.
> 
>  Documentation/git-gc.txt |    5 +++++
>  1 files changed, 5 insertions(+), 0 deletions(-)
> 
> diff --git a/Documentation/git-gc.txt b/Documentation/git-gc.txt
> index a9e0882..a514c52 100644
> --- a/Documentation/git-gc.txt
> +++ b/Documentation/git-gc.txt
> @@ -137,6 +137,11 @@ If you are expecting some objects to be collected and they aren't, check
>  all of those locations and decide whether it makes sense in your case to
>  remove those references.
>  
> +HOOKS
> +-----
> +This command can run `pre-auto-gc` hook.  See linkgit:githooks[5] for more
> +information.
> +
>  SEE ALSO
>  --------
>  linkgit:git-prune[1]

  reply	other threads:[~2010-06-28 18:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28 16:10 notify alternative to auto gc? Karl Stenerud
2010-06-28 16:26 ` Ævar Arnfjörð Bjarmason
2010-06-28 16:52   ` Karl Stenerud
2010-06-29  6:46     ` Matthieu Moy
2010-06-30  2:27   ` Sam Vilain
2010-06-28 16:27 ` Matthieu Moy
2010-06-28 16:29 ` Chris Packham
2010-06-28 16:56   ` Karl Stenerud
2010-06-28 17:07   ` [PATCH/RFC] Documentation/git-gc.txt: add reference to githooks Chris Packham
2010-06-28 18:43     ` Marc Branchaud [this message]
2010-06-29 15:43       ` Junio C Hamano
2010-06-29 16:00         ` Chris Packham
2010-06-29 16:26     ` Junio C Hamano
2010-06-29 18:16       ` Chris Packham
2010-06-30 20:41         ` [PATCHv2] " Chris Packham
2010-09-21 18:14     ` [PATCH/RFC] " David Brown
2010-09-21 20:52       ` Allow git remote add but not git clone ( was Re: [PATCH/RFC] Documentation/git-gc.txt: add reference to githooks) Chris Packham
2010-09-21 21:01         ` David Brown
2010-09-21 23:18       ` Re* [PATCH/RFC] Documentation/git-gc.txt: add reference to githooks Junio C Hamano
2010-06-28 18:58   ` notify alternative to auto gc? Eric Raible
2010-06-28 19:02     ` Jacob Helwig

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=4C28ED49.90906@xiplink.com \
    --to=marcnarc@xiplink.com \
    --cc=git@vger.kernel.org \
    --cc=judge.packham@gmail.com \
    --cc=spearce@spearce.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).