Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 01EB76337A6 for ; Wed, 27 May 2009 13:04:49 -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 12091-01; Wed, 27 May 2009 13:04:43 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 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 0DD886336C7; Wed, 27 May 2009 13:04:43 -0300 (ADT) Received: by bwz7 with SMTP id 7so4979198bwz.19 for ; Wed, 27 May 2009 09:04:42 -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=ifs2eK+OdmG2a0OwrmoJ+SD+zNVfSpntq0mj7dzR/wA=; b=iaPgn1h+zs0YUSKI6w0pEbpFY0atQ20Xz26UMMdJDgaypEtWD/o0116DxdrxJLrXpL AuTPlpYAbIzVP8SgROm3bArb99eULm1X5TFRjGj04HUqd2Unu0lmYpaGFNp/Us6XgqF6 OUBfbn6cHyG13e7Nl487pVvl+UKMcxjR95yqE= 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=V0QIXIZ8ePr3f/aHm4rmeXzSwaUcL6L/tuUlPfykrfA0HVJ6LVNewhocFTxhZO92e/ Dqr+1K8j0crMnUgfRDU95qpswoJBKT3v0aUopDVWHM7JgQRNHKWXyd8uhySXTGecElyv keFqpS7BF9YmPt5OHxi8NvK9/+rEXB+SUKAr8= MIME-Version: 1.0 Received: by 10.204.100.70 with SMTP id x6mr111894bkn.140.1243440281522; Wed, 27 May 2009 09:04:41 -0700 (PDT) In-Reply-To: <4A1D5FE9.90408@bluegap.ch> References: <937d27e10904270840vaf70c0fr37518478b31d8a15@mail.gmail.com> <200905271018.52381.peter_e@gmx.net> <20090527122514.1042356byix4x62y@mail.bluegap.ch> <200905271517.59781.peter_e@gmx.net> <4A1D5FE9.90408@bluegap.ch> Date: Wed, 27 May 2009 12:04:41 -0400 Message-ID: <603c8f070905270904n7b48a789u82bf62d8f6bbab0d@mail.gmail.com> Subject: Re: PostgreSQL Developer meeting minutes up From: Robert Haas To: Markus Wanner Cc: Peter Eisentraut , Magnus Hagander , Andrew Dunstan , Tom Lane , Stephen Frost , Josh Berkus , Dave Page , Bruce Momjian , David Fetter , Denis Lussier , Dimitri Fontaine , Greg Sabino Mullane , Greg Smith , Gregory Stark , Jan Wieck , Joshua Tolley , Koichi Suzuki , Marko Kreen , Michael Meskes , Oleg Bartunov , Robert Treat , Selena Deckelmann , Tatsuo Ishii , Teodor Sigaev , Toru SHIMOGAKI , Zdenek Kotala , PostgreSQL-development Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.182 tagged_above=0 required=5 tests=AWL=0.182 X-Spam-Level: X-Archive-Number: 200905/1118 X-Sequence-Number: 138660 On Wed, May 27, 2009 at 11:44 AM, Markus Wanner wrote: > Peter Eisentraut wrote: >>> In what way do you consider the tags "broken"? >> The tag applies to different commits on different files. > That's perfectly valid for CVS (and can be represented in subversion as > well). Such a tag cannot (easily) be converted to git, though (nor > mercurial or monotone), where tags are attached to a single commit. [...] > You (as well as myself, BTW) seem to think of a tag like something > that's attached to a single commit. I think this is a semantic argument. The problem isn't that we don't understand how CVS behaves; it's that we find that behavior undesirable, aka broken. If we really care about having a tag that contains the exact files that are tagged in CVS, we can create a branch from one of the commits involved, and then apply a commit to that branch that places it in the state that matches the contents of the CVS tag. AIUI, this is not very different from what you'd have to do in Subversion, where a tag is a branch is a copy. ...Robert