Tom Lane escribió: > Andrew Dunstan <and...@dunslane.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.
It would be great to have documented procedures for fixing fat-fingered commit messages and similar problems, though. Right now we have to live with redundant commits or replies on the pgsql-committers list. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
