Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 6E2A96357D5 for ; Thu, 28 May 2009 11:56:17 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 25844-04 for ; Thu, 28 May 2009 11:56:15 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-bw0-f163.google.com (mail-bw0-f163.google.com [209.85.218.163]) by mail.postgresql.org (Postfix) with ESMTP id B9288634722 for ; Thu, 28 May 2009 11:53:16 -0300 (ADT) Received: by bwz7 with SMTP id 7so5723292bwz.19 for ; Thu, 28 May 2009 07:53:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=9PLtGSSqY+64OBVExQuCjKuJSzvKbGuLcgmFjA5lG/8=; b=T2s9no1uHR2cntvOYK7RadeQ9uY2pqqAtTaWFHb+i9qZ37TcY5UYdLYWRoQAlM5nZG /40SQHwu5s4PR+5czgwJAgOfm0F+KWRpmyM7Kewt/zsbU3ugf1fuSFPQEcXESrIGqcku DRh/VFMv7gRy20WJqG8XbtvA3WoF4UUoDi+8g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=PnFXg+ADzqhsMA2XEoYlhbT7tVHKdonpTNt+A27YYDjC0m2mEzd4wPYJV/MAiRYhO+ ProxNtQnXtF2BZtnufGrv6Yvkb5pZhwPmXVJukdWKgSHLiTMLpTQ5uLlNaNRPetf8Q9U HfBTCJJP5gjIcz9avNJVfpHz/tEfYucb3bZoo= MIME-Version: 1.0 Received: by 10.204.103.203 with SMTP id l11mr1286517bko.71.1243522390749; Thu, 28 May 2009 07:53:10 -0700 (PDT) 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> Date: Thu, 28 May 2009 10:53:10 -0400 Message-ID: <603c8f070905280753mdf23e5aue75aefad029252e3@mail.gmail.com> Subject: Re: PostgreSQL Developer meeting minutes up From: Robert Haas To: Aidan Van Dyk Cc: Heikki Linnakangas , Magnus Hagander , Markus Wanner , Andrew Dunstan , PostgreSQL-development Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200905/1242 X-Sequence-Number: 138784 On Thu, May 28, 2009 at 10:18 AM, Aidan Van Dyk wrote: > * Robert Haas [090528 09:49]: >> On Thu, May 28, 2009 at 8:59 AM, Aidan Van Dyk 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. =A0Its >> > certainly not necessary, and possibly not even desirable... =A0Postgre= SQL >> > 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. =A0The git repository will have no history, and >> > people can choose which history they want to graft in... =A0CVSROOT ca= n be >> > made available as a historical download. >> >> That would suck for me. =A0I 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