pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Markus Wanner <markus@bluegap.ch>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Ron Mayer <rm_pg@cheapcomplexdevices.com>
Cc: Marko Kreen <markokr@gmail.com>
Cc: Greg Stark <stark@enterprisedb.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: Aidan Van Dyk <aidan@highrise.ca>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PostgreSQL Developer meeting minutes up
Date: Sat, 06 Jun 2009 17:41:10 +0200
Message-ID: <4A2A8E16.2090703@bluegap.ch> (raw)
In-Reply-To: <4A2922E8.1090505@dunslane.net>
References: <20090526144812.GC15213@yugib.highrise.ca>
	<e51f66da0906020546l578e56c8m52f5a6e10760eaf9@mail.gmail.com>
	<20090602162333.369974jcc3jpn3dx@mail.bluegap.ch>
	<e51f66da0906020834q7e6e3401jf77f40f9924bbace@mail.gmail.com>
	<20090602180702.15986cp384yo3l7q@mail.bluegap.ch>
	<e51f66da0906020917m274debd5u3288d6d56b62daf7@mail.gmail.com>
	<20090603131004.12934iyrr4f7rlsc@mail.bluegap.ch>
	<4136ffa0906030508i2971790dk54a8203ee03ed196@mail.gmail.com>
	<4A266A56.2020703@anarazel.de>
	<4136ffa0906030701x200bf0e4o4c77fa3239062ca5@mail.gmail.com>
	<e51f66da0906030720u33d72d05y14ea5ce002cbaf1e@mail.gmail.com>
	<20090604114610.808217tbogts0noi@mail.bluegap.ch>
	<4A283A8D.8030600@cheapcomplexdevices.com>
	<20090605090514.11712ntlvhi2deay@mail.bluegap.ch>
	<2871.1244209112@sss.pgh.pa.us>
	<4A2922E8.1090505@dunslane.net>

Hi,

Andrew Dunstan wrote:
> Yeah, a requirement to work from the back branch forward is quite
> unacceptable IMNSHO. It's also quite unreasonable.

The monotone page about daggy fixes does quite a good job in explaining
why it is helpful. I think it's how to make best use of these tools. And
it's obviously not the same as what worked well in practice with CVS.
Out of interest, and not necessarily related to Postgres: why do you
think it's unreasonable? Fixing the problem where it was introduced
sounds like the most reasonable place to fix it, IMO.

Regards

Markus Wanner



view thread (83+ messages)  latest in thread

Message-ID: <4A2A8E16.2090703@bluegap.ch>
Permalink:  ../4A2A8E16.2090703@bluegap.ch/
Also on:    postgresql.org/message-id/4A2A8E16.2090703@bluegap.ch

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: markus@bluegap.ch, andrew@dunslane.net, tgl@sss.pgh.pa.us, rm_pg@cheapcomplexdevices.com, markokr@gmail.com, stark@enterprisedb.com, andres@anarazel.de, aidan@highrise.ca, heikki.linnakangas@enterprisedb.com, magnus@hagander.net
  Subject: Re: PostgreSQL Developer meeting minutes up
  In-Reply-To: <4A2A8E16.2090703@bluegap.ch>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox