Re: [Gforge-admins] Permission problems on pgfoundry

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, gforge-admins(at)pgfoundry(dot)org, pgsql-www(at)postgresql(dot)org
Subject: Re: [Gforge-admins] Permission problems on pgfoundry
Date: 2009-07-02 02:24:55
Message-ID: 200907020224.n622Ot503261@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

Tom Lane wrote:
> "Andrew Dunstan" <andrew(at)dunslane(dot)net> writes:
> > What is the root of this checked out repo? It needs to be
> > /cvsroot/pg-migrator, not plain /cvsroot as set out here:
> > <http://pgfoundry.org/scm/?group_id=1000235>
>
> Hmm ... Bruce has been complaining of problems committing files in the
> top level of the repo. Maybe this is the cause?

I use this command:

cvs -q -d :ext:bmomjian(at)cvs(dot)pgfoundry(dot)org:/cvsroot/pg-migrator

so I should be OK. My problem is that if a subdirectory and the
top-level directory both have modified files, the commit message editor
shows all files as modified, but only the subdirectory files get changed
in CVS; I have to run cvs commit again to apply the top-level changes.
I have tried re-checking out the CVS tree but it didn't help.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-www by date

  From Date Subject
Next Message Dave Page 2009-07-02 07:58:36 Re: 8.4 Features Page Typos
Previous Message Erik Rijkers 2009-07-02 01:07:28 Re: 8.4 Features Page Typos