Re: CVS should die

From: Thomas Hallgren <thhal(at)mailblocks(dot)com>
To: Joerg Hessdoerfer <Joerg(dot)Hessdoerfer(at)sea-gmbh(dot)com>
Cc: PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CVS should die
Date: 2004-11-05 12:28:25
Message-ID: thhal-0jQpnApsy30A/QYjTBlKg516sBTOCt+@mailblocks.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Joerg Hessdoerfer wrote:
> <Advocacy>
> Yes, some do. At least SVN (Subversion) can handle moves very well, and
> especially it doesn't loose history on moves/renames.
> SVN holds it's repo entries in a database like 'filesystem', which can be
> backed by BDB4 or flat files (as of 1.1).
> SVN has proven to be stable in many OSS projects, and vastly superior over CVS
> especially in handling multi-GB projects containing binary files in our
> company.
>
> I refrain from listing all the advantages, if interested, have a look for
> yourself at http://subversion.tigris.org
>
> </Advocacy>
<MoreAdvocacy>
Another compelling reason to use SVN is that one of their long term
goals is to use an SQL backend. PostreSQL must be the absolute best
choice for that, right? So knowledge of SVN and some future
collaboration could perhaps be beneficial for both parties.

SVN is also targeted as a CVS replacement and a CVS user will feel very
much at home.
</MoreAdvocacy>

Regards,
Thomas Hallgren

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Neil Conway 2004-11-05 12:33:06 Re: [pgsql-www] pg_autovacuum is nice ... but ...
Previous Message John Hansen 2004-11-05 12:09:58 unnest

Browse pgsql-patches by date

  From Date Subject
Next Message Neil Conway 2004-11-05 12:36:32 Re: [PATCHES] CVS should die
Previous Message Markus Bertheau 2004-11-05 11:31:24 contrib/xml2: add function xml_encode_special_chars