| From: | Dave Page <dpage(at)postgresql(dot)org> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-www(at)postgresql(dot)org, Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, josh(at)agliodbs(dot)com |
| Subject: | Re: New pgsql-advocacy description |
| Date: | 2007-11-16 20:20:55 |
| Message-ID: | 473DFBA7.2090901@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
Joshua D. Drake wrote:
> On Fri, 16 Nov 2007 19:55:46 +0000
> Dave Page <dpage(at)postgresql(dot)org> wrote:
>
>>> Should I just push a branch?
>> Eh? The code's not even in SVN yet. My point is that with SVN we can
>> delete the old code and replace it with the new much more cleanly than
>> we could with CVS, thus it's no big deal to add whats there now and
>> replace it later.
>
>> Or are you suggesting a dev branch for me to put the new code in so
>> others can work on it until it's ready?
>
> Well that would work too :) what I was suggesting is getting the
> current archives code into the pgweb svn as a branch.
Nah, I'd put it under /trunk/archives. I'll need to look and see what
the best way to approach it is though. I'm not going to get to it right
away though - feel free to assign a ticket to me and I'll try to do
something next week.
As for the new code, that makes some sense to add as a branch, if only
so others can look and poke fun at it etc.
/D
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2007-11-16 20:42:16 | Archive generation scripts |
| Previous Message | Joshua D. Drake | 2007-11-16 20:06:02 | Re: duplicate entry on: http://www.postgresql.org/support/professional_support_northamerica |