On Mon, May 3, 2010 at 17:55, Andrew Dunstan <and...@dunslane.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/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
