Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id C6BB063519D for ; Tue, 2 Jun 2009 12:45:05 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 09010-01-5 for ; Tue, 2 Jun 2009 12:45:03 -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 EBE8A63509A for ; Tue, 2 Jun 2009 12:44:59 -0300 (ADT) Received: by bwz7 with SMTP id 7so8645814bwz.19 for ; Tue, 02 Jun 2009 08:44:58 -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=5GFL9yBTm3QZ7RPUl69SqmELXZbzllfM1LdAOeLtjYc=; b=bgCICy9Ibwnl0eHUXL3uE77KGv6yzcyZzWxebUcICe9L+gWpqcsSJvzSddHV0UkizG tlFEgyf4JMgTsi510Vyzo9qqg9w0Hash8f8hG79OLP+Q2hpa9FCkZaP3vl5s8cp/wJdH n4noND2BU/ALmBn+kkshJQiFsggy/Pq8Kb9Vk= 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=s1tzq5+Wc6tNpZEwrDlXf47HVhRalKCLhyyPuP6IRAhn7Tbkpkq4mxcOVeexVfFlly YEF4zuU15LPkV1+OeppiU0l3V05Tamj3/qn2Qzmj9UBq/UW8tBJRZYar1Evo4s+V3N1n O7DCChpdA8UTQ+N9jfrF40QkROgt3itIgvviE= MIME-Version: 1.0 Received: by 10.204.57.79 with SMTP id b15mr7049078bkh.70.1243957498489; Tue, 02 Jun 2009 08:44:58 -0700 (PDT) In-Reply-To: <12583.1243955294@sss.pgh.pa.us> References: <20090529170559.99155w414h94hazb@mail.bluegap.ch> <20090529153435.GA15213@yugib.highrise.ca> <4A241340.9080903@bluegap.ch> <20090602134831.186767ksvmsgj8gf@mail.bluegap.ch> <20090602162333.369974jcc3jpn3dx@mail.bluegap.ch> <20090602145000.GE23972@yugib.highrise.ca> <12583.1243955294@sss.pgh.pa.us> Date: Tue, 2 Jun 2009 11:44:58 -0400 Message-ID: <603c8f070906020844x2a26f307v72169ceeb52dc612@mail.gmail.com> Subject: Re: PostgreSQL Developer meeting minutes up From: Robert Haas To: Tom Lane Cc: Aidan Van Dyk , Markus Wanner , Marko Kreen , Heikki Linnakangas , Magnus Hagander , 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.146 tagged_above=0 required=5 tests=AWL=0.146 X-Spam-Level: X-Archive-Number: 200906/167 X-Sequence-Number: 139222 On Tue, Jun 2, 2009 at 11:08 AM, Tom Lane wrote: > Aidan Van Dyk writes: >> * Markus Wanner [090602 10:23]: >>> You consider it a mess, I consider it a better and more valid >>> representation of the mess that CVS is. > >> So much better that it makes the history as useless as CVS... I think >> one of the reasons people are wanting tomove from CVS to git is that it >> makes things *better*... > > FWIW, the tool that I customarily use (cvs2cl) considers commits on > different branches to be "the same" if they have the same commit message > and occur sufficiently close together (within a few minutes). =A0My > committing habits have been designed around that behavior for years, > and I believe other PG committers have been doing likewise. Interesting. I was wondering why all your commit messages always show up simultaneously for all the back branches. > I would consider a git conversion to be less useful to me, not more, > if it insists on showing me such cases as separate commits --- and if > it then adds useless "merge" messages on top of that, I'd start to get > seriously annoyed. There's no help for them being separate commits, but I agree that useless merge commits are a bad thing. There are plenty of ways to avoid that, though; I've been using git cherry-pick a lot recently, and I think git rebase --onto also has some potential. ...Robert