Re: Git cvsserver serious issue - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Git cvsserver serious issue
Date
Msg-id 24873.1285255006@sss.pgh.pa.us
Whole thread Raw
In response to Git cvsserver serious issue  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Git cvsserver serious issue  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> So, I found (with some helpful hints from Robert who caught the final
> nail in the coffin) a good reason why we really can't run a
> git-cvsserver globally.

> Any user can point their cvs client at the repository. And check out
> an arbitrary branch, tag *or individual commit*. Doing so will create
> a 50Mb sqlite database on the server with cache information about that
> head.

I'm still wondering why we don't simply lobotomize git-cvsserver to
refuse requests to check out anything except the active branch tips.
It's only a Perl script.  I could probably hack it in an hour,
there are those here who could do it in ten minutes.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Serializable Snapshot Isolation
Next
From: Andrew Dunstan
Date:
Subject: Re: Git cvsserver serious issue