On Thu, May 28, 2009 at 10:18 AM, Aidan Van Dyk <ai...@highrise.ca> wrote: > * Robert Haas <robertmh...@gmail.com> [090528 09:49]: >> On Thu, May 28, 2009 at 8:59 AM, Aidan Van Dyk <ai...@highrise.ca> wrote: >> > All that based on the assumption that when the project switches to git, >> > they actually want all the CVS history in their official tree. Its >> > certainly not necessary, and possibly not even desirable... PostgreSQL >> > could just as easily to a "linus" style switch when they switch to git, >> > and just "import" the latest release in each branch as the starting >> > point for each branch. The git repository will have no history, and >> > people can choose which history they want to graft in... CVSROOT can be >> > made available as a historical download. >> >> That would suck for me. I use git log a lot to see how things have >> changed over time. > > No, the whole point is that you graft whatever history *you* want in... > So if PostgreSQL "offical" git only starts when the offical VCS was in > git, you graft on gpo, or git, or some personal one-time cvs2git or > parsecvs history you want in...
I want the project infrastructure to do this for me so I don't have to do anything except git clone. It's not a big deal for me to port my WIP over to a new git repo if this one is busted, which it sounds like it is. But I'm not interested in rolling my own history. ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
