Re: PostgreSQL Developer meeting minutes up - Mailing list pgsql-hackers

From Markus Wanner
Subject Re: PostgreSQL Developer meeting minutes up
Date
Msg-id 20090528181016.20761ewel8xikmzs@mail.bluegap.ch
Whole thread Raw
In response to Re: PostgreSQL Developer meeting minutes up  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: PostgreSQL Developer meeting minutes up  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Hi,

Quoting "Robert Haas" <robertmhaas@gmail.com>:
> My understanding is that the histories of some of the branches we have
> now are flat-out wrong.

AFAIU only the latest revisions of the branches have been compared.
Keeping history and future in mind, that's not telling much, IMO. In
my experience, there's much more wrong with converted CVS repositories
- the latest revisions are often just the tip of the iceberg.
Depending on your definition of "wrong", of course.

> I don't have a problem keeping those
> alongside the corrected history for ease of rebasing and porting
> commits, but I don't want to punt the problem of figuring out what the
> one, true, and correct history is to the user.

Understood and agreed. (In a distributed VCS, you cannot "delete"
history by definition, because every user is free to keep his version).

However, I'm pretty certain this is not the last "flat-out wrong"
thing we find in the CVS or in the converted git repository. Going to
fix and rebase every time might be pretty annoying and time consuming.
Thus alternatives like those mentioned by Aidan sound interesting to me.

Regards

Markus Wanner


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Clean shutdown and warm standby
Next
From: Dmitry Koterov
Date:
Subject: Re: Fast ALTER TABLE ... ADD COLUMN ... DEFAULT xxx?