Re: Git cvsserver serious issue

On 10/08/2010 09:15 AM, Marko Kreen wrote:
> On Fri, Oct 8, 2010 at 3:13 PM, Andrew Dunstan<andrew@dunslane.net>  wrote:
>> On 10/08/2010 02:09 AM, Magnus Hagander wrote:
>>> On Fri, Oct 8, 2010 at 03:52, Andrew Dunstan<andrew@dunslane.net>    wrote:
>>>> There's a simpler solution which I have just tested. Instead of patching,
>>>> use the Pg driver instead of SQLite. Set the dbname to %m. If the
>>>> database
>>>> doesn't exist the cvs checkout will fail. So we just set up databases for
>>>> the modules we want to export (master and RELn_m_STABLE for the live
>>>> branches).
> Wouldn't it be simpler be to generate hourly tarball on some host and wget it?
> It can be generated even more often, as no history need to be kept.
>
> Considering the state of cvsserver, can you be certain that whatever
> is coming from it is really the most recent code?

Sure you can, why not? It will be coming from the same git repo that 
servers git requests. git-cvsserver doesn't create a new CVS repo, it 
emulates CVS from a git repo.

cheers

andrew