[Bryan O'Sullivan]
> > The centralised SCM tools all create a wall between core developers
> > (i.e. people with commit access to the central repository) and
people
> > who are on the fringes. Outsiders may be able to get anonymous
> > read-only access, but they are left up to their own devices i
On Mon, 2005-08-15 at 23:29 +0200, "Martin v. Löwis" wrote:
> That may be off-topic for python-dev, but can you please explain how
> this works?
It's simple enough. In place of a central server that hosts a set of
repositories and a number of branches, and to which only a few people
have access,
Bryan O'Sullivan wrote:
> However, it's worth pointing out that with a distributed SCM - it
> doesn't really matter which one you use - it is simple to put together a
> workflow that operates in the same way as a centralised SCM. You lose
> nothing in the translation. What you gain is several-fol
On Aug 15, 2005, at 5:04 PM, Bryan O'Sullivan wrote:
> The centralised SCM tools all create a wall between core developers
> (i.e. people with commit access to the central repository) and people
> who are on the fringes. Outsiders may be able to get anonymous
> read-only access, but they are left
Pardon me for coming a little late to the SCM discussion, but I thought
I would throw a few comments in.
A little background: I've used Perforce, CVS, Subversion and BitKeeper
for a number of years. Currently, I hack on Mercurial
http://www.selenic.com/mercurial>.
However, I'm not here to try an
