From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: Proposal to shutdown pgFoundry |
Date: | 2011-05-20 16:01:36 |
Message-ID: | 1305907268-sup-4997@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Excerpts from Dave Page's message of vie may 20 11:48:58 -0400 2011:
> 2011/5/20 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> > I need to figure out what to do with pg_filedump. All I need for it
> > is an SCM and someplace to put release tarballs. I'd prefer to use
> > git.postgresql.org, but if there's nowhere for tarballs, that's not
> > going to work.
>
> Hmm, that's a good example. It would certainly qualify to live on
> git.postgresql.org using the criteria I have in mind, but I can see
> the tarballs would be an issue. If we do keep git.postgresql.org for
> trusted projects, then perhaps it wouldn't be such an issue to give
> certain users from each one access to a server to upload tarballs into
> the mirror network.
So how does pgadmin deal with tarballs and installers etc? Do they have
their own server for that?
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Kaltenbrunner | 2011-05-20 16:20:32 | Re: Proposal to shutdown pgFoundry |
Previous Message | Dave Page | 2011-05-20 15:48:58 | Re: Proposal to shutdown pgFoundry |