Re: documentation for committing with git

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: documentation for committing with git
Date: 2010-08-05 09:35:59
Message-ID: 4C5A85FF.60107@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 04/08/10 16:50, Andrew Dunstan wrote:
> On 08/04/2010 09:29 AM, Heikki Linnakangas wrote:
>>
>> All those issues can be avoided if you only run "git gc" when all the
>> working directories are in a clean state, with no staged but
>> uncommitted changes or other funny things. I can live with that gun
>> tied to my ankle ;-).
>
> But to make sure of that I think you need to prevent git commands from
> running gc automatically:
>
> git config gc.auto 0
>
> or possibly
>
> git config --global gc.auto 0
>
> And you'll need to make sure you run gc yourself from time to time.

Good idea. I'll add that to the wiki. I don't like the automatic garbage
collection anyway, it always kicks in when I'm doing something, and I
end up interrupting it anyway.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2010-08-05 09:39:13 Re: string_agg delimiter having no effect with order by
Previous Message Greg Stark 2010-08-05 09:29:42 Re: string_agg delimiter having no effect with order by