From: Robert Haas <robertmhaas@gmail.com>
To: Aidan Van Dyk <aidan@highrise.ca>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Markus Wanner <markus@bluegap.ch>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PostgreSQL Developer meeting minutes up
Date: Thu, 28 May 2009 10:53:10 -0400
Message-ID: <603c8f070905280753mdf23e5aue75aefad029252e3@mail.gmail.com> (raw)
In-Reply-To: <20090528141827.GT15213@yugib.highrise.ca>
References: <20090526144812.GC15213@yugib.highrise.ca>
<4A1D1E64.6030908@hagander.net>
<4A1D2290.7060907@enterprisedb.com>
<20090527212240.GP15213@yugib.highrise.ca>
<603c8f070905271829i9458bdftcaed2dadb0a74583@mail.gmail.com>
<20090528020909.GQ15213@yugib.highrise.ca>
<603c8f070905271942ke9df2aah8648fe4d1228d43e@mail.gmail.com>
<20090528125944.GS15213@yugib.highrise.ca>
<603c8f070905280649m5d5fc458se54435dfe20cc7ca@mail.gmail.com>
<20090528141827.GT15213@yugib.highrise.ca>
On Thu, May 28, 2009 at 10:18 AM, Aidan Van Dyk <aidan@highrise.ca> wrote:
> * Robert Haas <robertmhaas@gmail.com> [090528 09:49]:
>> On Thu, May 28, 2009 at 8:59 AM, Aidan Van Dyk <aidan@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
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: robertmhaas@gmail.com, aidan@highrise.ca, heikki.linnakangas@enterprisedb.com, magnus@hagander.net, markus@bluegap.ch, andrew@dunslane.net
Subject: Re: PostgreSQL Developer meeting minutes up
In-Reply-To: <603c8f070905280753mdf23e5aue75aefad029252e3@mail.gmail.com>
* 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