Re: missing file in git repo

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Aidan Van Dyk <aidan(at)highrise(dot)ca>, Magnus Hagander <magnus(at)hagander(dot)net>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Alexey Klyukin <alexk(at)commandprompt(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "cedric(dot)villemain(dot)debian" <cedric(dot)villemain(dot)debian(at)gmail(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: missing file in git repo
Date: 2010-05-03 15:55:24
Message-ID: 4BDEF1EC.1060809@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas wrote:
> Heikki and I are both BIG git users, and I think Andrew, Simon, and
> Alvaro all use it too, though I'm not sure to what extent.
>

I am using it increasingly. Of course, I need to convert some of my
customers ....

> A couple of random things I'm concerned about:
>
> - the buildfarm, obviously, has got to work
>

That work is almost complete. My plan is to unveil it all in my talk at
pgcon.

> - we need to make sure that all the committers understand how to keep
> the history the way we want it - i.e. linear, without merges, and
> possibly even implement programmatic safeguards against doing anything
> else
>
>
>

That too will be part of my talk. I'm not sure how you would implement
such programmatic safeguards, though. We don't have such a huge
population of committers that we can't manage this by education, I think.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Selena Deckelmann 2010-05-03 16:07:25 Re: Re: Mailing list archives (was Re: [HACKERS] mailing list archiver chewing patches)
Previous Message Tom Lane 2010-05-03 15:37:04 max_standby_delay considered harmful