Re: Not ready for 8.3

From: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Greg Smith <gsmith(at)gregsmith(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Not ready for 8.3
Date: 2007-05-19 15:51:29
Message-ID: 464F1D01.2030908@phlo.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan wrote:
> What would making a branch actually do for you? The only advantage I can
> see is that it will give you a way of checkpointing your files. As I
> remarked upthread, I occasionally use RCS for that. But mostly I don't
> actually bother. I don't see how you can do it reasonably off a local
> cvs mirror - rsync will just blow away any changes you have checked in
> next time you sync with the master.
>
> I don't think we can make CVS behave like a distributed SCM system, and
> ability to create local branches seems to me one of the fundamental
> points of such systems. If that's what the demand is for, then we should
> look again at moving to something like Mercurial.

I think the great thing about DCVS systems is that not everybody
necessarily needs to use the *same* system. And it doesn't really
matter what the central repository runs on - I think they are
gateway from/to nearly everything available...

I currently use GIT for my SoC project, and it works quite well -
I can create an abitrary number of local branches, and syncing
the currently active branch with CVS is archived by just doing
"cg-update pgsql-head".

greetings, Florian Pflug

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Shachar Shemesh 2007-05-19 17:05:43 Re: [Oledb-dev] double precision error with pg linux server, but not with windows pg server
Previous Message Arjen van der Meijden 2007-05-19 14:12:04 Re: Reducing stats collection overhead