2010/1/17 Peter Eisentraut <[email protected]>: > On sön, 2010-01-17 at 20:50 +0100, Magnus Hagander wrote: >> As for fixing it, I guess we can try the >> rewind-to-commit-before-this-and-rerun. That'll break people who have >> branched after, but last time it seemed that most peoples git clients >> would clean that up automatically. Which commits are these exactly? > > These two belong together: > > http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/start-scripts/freebsd?rev=1.5 > http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/start-scripts/osx/PostgreSQL?rev=1.4 > > And this is a separate one: > > http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/config/python.m4?rev=1.17 Well, if we're going to roll something back in git, it's the git comits that are interesting... To figure out how far back in time to go. -- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/
pgsql-hackers by date:
Соглашаюсь с условиями обработки персональных данных
