Re: Git cvsserver serious issue

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Git cvsserver serious issue
Date: 2010-09-23 15:16:46
Message-ID: 24873.1285255006@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: buildfarm-members pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)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

In response to

Responses

Browse buildfarm-members by date

  From Date Subject
Next Message Andrew Dunstan 2010-09-23 15:17:35 Re: Git cvsserver serious issue
Previous Message David Fetter 2010-09-23 14:58:02 Re: Git cvsserver serious issue

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2010-09-23 15:17:35 Re: Git cvsserver serious issue
Previous Message Kevin Grittner 2010-09-23 15:08:34 Re: Serializable Snapshot Isolation