Re: missing file in git repo

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, 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 16:31:47
Message-ID: r2z9837222c1005030931kf1643951m809b4dc91337cd6d@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 3, 2010 at 17:55, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> 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.

It's pretty trivial to block some of the most error-prone things. I
believe it's even in there as a sample somewhere. I thought you were
the one supposed to teach us this :-P

Anyway, I think it's worth putting in, at least the simple ones. It's
easier than cleaning up after a single mistake, most likely...

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2010-05-03 16:32:11 Re: Re: Mailing list archives
Previous Message Tom Lane 2010-05-03 16:26:55 Re: missing file in git repo