| 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(dot) Fournier" <scrappy(at)hub(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Strange anoncvs sync behavior |
| Date: | 2007-10-29 10:16:24 |
| Message-ID: | 200710291116.25147.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2007-10-29 13:43:11 | Announce list |
| Previous Message | Magnus Hagander | 2007-10-29 06:27:33 | Re: Strange anoncvs sync behavior |