From: Chris Packham <judge.packham@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Marc Branchaud <marcnarc@xiplink.com>,
spearce@spearce.org, git@vger.kernel.org
Subject: Re: [PATCH/RFC] Documentation/git-gc.txt: add reference to githooks
Date: Tue, 29 Jun 2010 09:00:29 -0700 [thread overview]
Message-ID: <AANLkTilZsHJ20hGehY5eqOfS8jt--ne_QGp4z8SyNeUD@mail.gmail.com> (raw)
In-Reply-To: <7vsk45c09m.fsf@alter.siamese.dyndns.org>
On Tue, Jun 29, 2010 at 8:43 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Marc Branchaud <marcnarc@xiplink.com> writes:
>
>> How about also adding a templates/hooks--pre-auto-gc.sample file?
>
> Please don't, as samples are propagated to all newly created repositories.
>
OK. I won't add a sample hook.
next prev parent reply other threads:[~2010-06-29 16:00 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
2010-06-29 15:43 ` Junio C Hamano
2010-06-29 16:00 ` Chris Packham [this message]
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=AANLkTilZsHJ20hGehY5eqOfS8jt--ne_QGp4z8SyNeUD@mail.gmail.com \
--to=judge.packham@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=marcnarc@xiplink.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).