On Sun, 06 Mar 2011, Scott Kitterman wrote: > One thing that is a clear advantage for bzr is that it supports both a > traditional centralized workflow and modern DVCS workflow so that not > everyone > needs to switch to a foreign method of work immediately after the transition. >
AFAIK any DVCS could be used in a 'centralized' fashion -- just choose the central repository everyone should use for their pushes (e.g. like we would already have for team maintained packaging). Moreover git provides git cvsserver, so hard-core CVS users do not even need to switch away from CVS client. Personally, bzr always gave me creeps, and I never managed to get peace with HG (probably problem is in me, not in GIT). And despite being pro-Python myself, I hated all those tracebacks I received from HG and bzr -- most of the time they were close to useless for me as the user. -- =------------------------------------------------------------------= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110306200225.gg29...@onerussian.com