git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Junio C Hamano <gitster@pobox.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Bj?rn Steinbrink <B.Steinbrink@gmx.de>,
	git@vger.kernel.org
Subject: Re: tests for pre-auto-gc hook
Date: Fri, 04 Apr 2008 08:34:39 +0200	[thread overview]
Message-ID: <47F5CBFF.1080807@viscovery.net> (raw)
In-Reply-To: <20080403212656.GJ11574@genesis.frugalware.org>

Miklos Vajna schrieb:
> I wanted to create a test like t7503-pre-commit-hook.sh for pre-auto-gc
> but actually I'm not sure how to trigger git gc --auto to do something.
> 
> Here is what I managed to do so far:
> 
> ----
> git init
> git config gc.auto 1
> for i in `seq 1 500`; do echo $i >file; git add file; done
> git commit -m init
> ----

Avoid 'seq'; it is not available everywhere. To avoid spawning 500
processes, you could create a pack file from the files using fastimport,
then unpack that for each test case. But you must move the pack out of
.git/objects/pack before unpacking, otherwise it won't unpack anything.

-- Hannes

  reply	other threads:[~2008-04-04  6:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7637ee64f43964d2e514c1598b2e7783d71b8608.1206929014.git.vmiklos @frugalware.org>
2008-04-01  4:51 ` [PATCH 1/4] git-gc --auto: add pre-auto-gc hook Junio C Hamano
2008-04-01 11:38   ` [PATCH 0/4] add pre-auto-gc hook for git-gc --auto (try2) Miklos Vajna
2008-04-01 23:18     ` Junio C Hamano
2008-04-02  1:14       ` Miklos Vajna
2008-04-02  4:02         ` Junio C Hamano
2008-04-02 19:02           ` Miklos Vajna
2008-04-02 19:07             ` Junio C Hamano
2008-04-02 19:34               ` [PATCH 0/3] add pre-auto-gc hook for git-gc --auto (try3) Miklos Vajna
2008-04-02 19:34               ` [PATCH 1/3] git-gc --auto: add pre-auto-gc hook Miklos Vajna
2008-04-02 19:34               ` [PATCH 2/3] Documentation/hooks: " Miklos Vajna
2008-04-02 19:35               ` [PATCH 3/3] contrib/hooks: add an example " Miklos Vajna
2008-04-02 19:49                 ` Junio C Hamano
2008-04-02 20:22                   ` Miklos Vajna
2008-04-02 20:34                     ` Junio C Hamano
2008-04-02 20:45                       ` Miklos Vajna
2008-04-03 21:26                         ` tests for pre-auto-gc hook (WAS: Re: [PATCH 3/3] contrib/hooks: add an example pre-auto-gc hook) Miklos Vajna
2008-04-04  6:34                           ` Johannes Sixt [this message]
2008-04-01 11:39   ` [PATCH 1/4] git-gc --auto: add pre-auto-gc hook Miklos Vajna
2008-04-01 11:39   ` [PATCH 2/4] Documentation/hooks: " Miklos Vajna
2008-04-01 11:39   ` [PATCH 3/4] templates: add an example " Miklos Vajna
2008-04-01 11:39   ` [PATCH 4/4] contrib/hooks: " Miklos Vajna

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47F5CBFF.1080807@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=B.Steinbrink@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vmiklos@frugalware.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).