Hi, Quoting "Robert Haas" <robertmh...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
