Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Strange anoncvs sync behavior
- From: Peter Eisentraut <peter_e(at)gmx(dot)net>
- To: pgsql-www(at)postgresql(dot)org
- Cc: Magnus Hagander <magnus(at)hagander(dot)net>, "Marc G. Fournier" <scrappy(at)hub(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Subject: Re: Strange anoncvs sync behavior
- Date: Mon, 29 Oct 2007 11:16:24 +0100
- Message-id: <200710291116(dot)25147(dot)peter_e(at)gmx(dot)net>
Am Montag, 29. Oktober 2007 schrieb Magnus Hagander: > >> You were hacking on the tag/branch stuff only to allow "pgsql" to do > >> that, but then IIRC people spoke up and said they wanted it the other > >> way around - only personal accounts doing it. Or something like that. > Ah, that's what I meant, really :-) At least in that being the reason > why I stopped looking at the other part, and then forgot about it. Would this have anything to do with this problem: $ cvs update -rREL8_2_STABLE cvs update: warning: cannot open /cvsroot/CVSROOT/val-tags read/write: Permission denied cvs update: failed to create lock directory for `/cvsroot/pgsql' (/cvsroot/pgsql/#cvs.lock): Permission denied cvs update: failed to obtain dir lock in repository `/cvsroot/pgsql' cvs [update aborted]: read lock failed - giving up -- Peter Eisentraut http://developer.postgresql.org/~petere/
- References:
- Strange anoncvs sync behavior
- From: Tom Lane
- Re: Strange anoncvs sync behavior
- From: Marc G. Fournier
- Re: Strange anoncvs sync behavior
- From: Magnus Hagander
- Strange anoncvs sync behavior
- Prev by Date: Re: Strange anoncvs sync behavior
- Next by Date: Announce list
- Previous by thread: Re: Strange anoncvs sync behavior
- Next by thread: Beta 2 sometime tommorrow
- Indexes: