"David E. Wheeler" <da...@kineticode.com> writes: > Perhaps there's a master repository that corresonds to CVS HEAD, and > then release branches are actually separate git repositories.
Yeah, I was speculating about that one too. It might be workable. Just "cp -r" the master whenever we fork a new branch. However, there'd be no very easy way to get a change history that includes patches that applied only to some back branches (something that does happen, a few times a year perhaps). Maybe that special log tool Andrew was speculating about would take the form of a program to aggregate the change histories of several repositories. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers