pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Marc G. Fournier <scrappy@hub.org>
To: Peter Eisentraut <peter_e@gmx.net>
To: pgsql-hackers@postgresql.org
Cc: Aidan Van Dyk <aidan@highrise.ca>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>
Subject: Re: PostgreSQL Developer meeting minutes up
Date: Thu, 28 May 2009 01:09:10 +0000
Message-ID: <306EEBC41F4E2BA856DDE879@ganymede.hub.org> (raw)
In-Reply-To: <200905271633.28594.peter_e@gmx.net>
References: <4A189843.3010200@agliodbs.com>
	<20090526153501.GG15213@yugib.highrise.ca>
	<20090526185313.T35116@hub.org>
	<200905271633.28594.peter_e@gmx.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



- --On Wednesday, May 27, 2009 16:33:28 +0300 Peter Eisentraut <peter_e@gmx.net> 
wrote:

> On Wednesday 27 May 2009 00:54:52 Marc G. Fournier wrote:
>> So, you are suggesting:
>>
>> cvs -q tag -d REL7_1_BETA2 .
>> cvs -q tag -d REL7_1_BETA3 .
>
> Note that there are actually two different issues related to tags:
>
> One is, the tags REL7_1_BETA2 and REL7_1_BETA3 cannot be parsed by cvsps.
> But  no one has analyzed why that is.  Nor is there any proof that they are
> wrong  or broken.

I'm curious as to what is different about these vs all the other tags I've ever 
done, both before, and after ...

> The other is, the tag REL7_1 produces different files than were actually in
> the release.  cvsps warns about this.  I had posted a patch to fix this.

Please repost ...





- -- 
Marc G. Fournier        Hub.Org Hosting Solutions S.A. (http://www.hub.org)
Email . scrappy@hub.org                              MSN . scrappy@hub.org
Yahoo . yscrappy               Skype: hub.org        ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)

iEYEARECAAYFAkod5DYACgkQ4QvfyHIvDvPfcgCfTCGz5JG5KmCQrbdx9+37l8sT
nFAAnjcH3oL11J5CIKR5ZIVHRtSe+MVj
=SE8O
-----END PGP SIGNATURE-----




view thread (74+ messages)  latest in thread

Message-ID: <306EEBC41F4E2BA856DDE879@ganymede.hub.org>
Permalink:  ../306EEBC41F4E2BA856DDE879@ganymede.hub.org/
Also on:    postgresql.org/message-id/306EEBC41F4E2BA856DDE879@ganymede.hub.org

 · 

reply

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: scrappy@hub.org, peter_e@gmx.net, aidan@highrise.ca, tgl@sss.pgh.pa.us, andrew@dunslane.net
  Subject: Re: PostgreSQL Developer meeting minutes up
  In-Reply-To: <306EEBC41F4E2BA856DDE879@ganymede.hub.org>

* 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