| From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Dave Page <dpage(at)pgadmin(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: snapshot generation broken |
| Date: | 2010-09-22 11:28:48 |
| Message-ID: | 4C99E870.9080507@kaltenbrunner.cc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander wrote:
> On Wed, Sep 22, 2010 at 13:20, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>> On ons, 2010-09-22 at 12:22 +0200, Magnus Hagander wrote:
>>> Mind you, I think bf members will need tweaking anyway, since they
>>> will assume the old style cvs layout. AFAICT, git-cvsserver will
>>> export each branch as a module, rather than one module as pgsql. We
>>> can obviously get that working for the HEAD branch (by just mapping it
>>> to a branch called pgsql), but I don't know how doable that is for
>>> backbranches.
>> We need to have a fix for this before we can do any more backbranch
>> releases.
>
> Fix for what, exactly? (assuming that people update their bf animals of course)
how exactly should people fix their BF members - is there any howto or
such on how to deal with the new git2cvs gateway?
Switching to git entirely is rather hard for some of my members for
example - at least not without investing hours of work...
Stefan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2010-09-22 11:30:06 | Re: BUG #5661: The character encoding in logfile is confusing. |
| Previous Message | Stefan Kaltenbrunner | 2010-09-22 11:27:24 | Re: snapshot generation broken |