| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | Maurice Gittens <mgittens(at)gits(dot)nl> |
| Cc: | hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] CVSup |
| Date: | 1998-05-01 11:22:00 |
| Message-ID: | Pine.NEB.3.95.980501072012.19987B-100000@hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 1 May 1998, Maurice Gittens wrote:
> Hi,
>
> I don't understand the problem CVSup is intended to solve given
> that CVS allows remote access to the repository using standard cvs
> commands. Is there a specific reason why we can't/don't have readonly access
> to the postgresql repository?
>
> I think it's neat to be able to use commands like "cvs diff" etc. However
> I really hate it that my changes seem to get overwritten why I using
> CVSup since this doesn't happen when using the "cvs update".
>
> Can anyone explain why this is the way it is?
When I set things up, I could find no instructions for setting up
anon-cvs that I felt comfortable implementing from a security
standpoint...
If you remove the 'tag=.' part of the CVSup config file, you can
pull down the complete CVS repository to your machine to manipulate as you
want to...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 1998-05-01 11:22:20 | Re: [HACKERS] CVSup |
| Previous Message | Peter Mount | 1998-05-01 07:12:00 | RE: [HACKERS] Re: CODE ANALYSIS FOR (an apparent error in answer from "##" (closest proximity)operator) |