| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, 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> |
| Subject: | Re: missing file in git repo |
| Date: | 2010-05-03 16:26:55 |
| Message-ID: | 17588.1272904015@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Robert Haas wrote:
>> - 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.
I agree that programmatic safeguards are probably overkill, as long as
we have some agreed-on, documented commit procedures. We've survived
fine without any such backstops for CVS commits.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-05-03 16:31:47 | Re: missing file in git repo |
| Previous Message | Selena Deckelmann | 2010-05-03 16:07:25 | Re: Re: Mailing list archives (was Re: [HACKERS] mailing list archiver chewing patches) |