Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id DFDDF632450 for ; Thu, 10 Jun 2010 13:20:37 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 40344-01 for ; Thu, 10 Jun 2010 16:20:30 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from tamriel.snowman.net (tamriel.snowman.net [72.66.115.51]) by mail.postgresql.org (Postfix) with ESMTP id 559FA63235F for ; Thu, 10 Jun 2010 13:20:30 -0300 (ADT) Received: by tamriel.snowman.net (Postfix, from userid 1000) id A46D022941; Thu, 10 Jun 2010 12:20:29 -0400 (EDT) Date: Thu, 10 Jun 2010 12:20:29 -0400 From: Stephen Frost To: Andrew Dunstan Cc: Stephen Frost , "Luxenberg, Scott I." , pgsql-hackers@postgresql.org Subject: Re: Error with GIT Repository Message-ID: <20100610162029.GI21875@tamriel.snowman.net> References: <9477.1267142614@sss.pgh.pa.us> <603c8f071003020816j77b3ec63wbad0415df003c0f1@mail.gmail.com> <17546.1267546998@sss.pgh.pa.us> <489.1276114285@sss.pgh.pa.us> <972101EB3500F64288D9FC67457ED97401164254@email1.mitretek.org> <4C110443.7060209@dunslane.net> <20100610154416.GV5699@saruman.tsf.noblis.org> <4C110FBC.6010009@dunslane.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="JhuwnVjsOW3cA1Qv" Content-Disposition: inline In-Reply-To: <4C110FBC.6010009@dunslane.net> X-Editor: Vim http://www.vim.org/ X-Info: http://www.snowman.net X-Operating-System: Linux/2.6.26-1-amd64 (x86_64) X-Uptime: 12:17:53 up 287 days, 3:42, 27 users, load average: 0.29, 0.15, 0.10 User-Agent: Mutt/1.5.18 (2008-05-17) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201006/611 X-Sequence-Number: 164241 --JhuwnVjsOW3cA1Qv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Andrew Dunstan (andrew@dunslane.net) wrote: > I don't see why not. Buildfarm members are going to have to reset their = =20 > repos when we finally cut over in a few months. Luckily, this is a =20 > fairly painless operation - blow away the repo and change the config =20 > file and the script will resync as if nothing had happened. Should we stop bothering to offer http://git.postgresql.org then..? Or do we expect it to get fixed and work correctly once we cut over and rebuild? Also, perhaps we could list the git-hub option on the wiki (http://wiki.postgresql.org/wiki/Other_Git_Repositories)? (and, yea, it's the same me) Thanks, Stephen --JhuwnVjsOW3cA1Qv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkwREM0ACgkQrzgMPqB3kiiwQACdEOeJ7ygsOnkX5nTx+2dKvHSa HUUAniNMnO9EmFp1ypVxD/ak1gH9Bv9g =0uMA -----END PGP SIGNATURE----- --JhuwnVjsOW3cA1Qv--