text_combined: stephen j turnbull xjzvfpwxemacsorg iybzpoboxcom writes distributed revision control systems available bzr hg darcs svk many find need introduction concepts advantages repository distribution someone point useful content web pages books help wrap brain around ideas maybe comparecontrast major players others mentioned bunch resources theyre ok reassure dvcs different youre used ill post comments far know existing resources one caveat careful reading command involves receiving changes remote repo updating workspace terms like get fetch pull update clone even checkout commonly used describe operations actual semantics commands named terms differs wildly example git fetch receives metadata new content pull fetch attempts update workspace performs 3way merges mercurial pull fetch opposite semantics also note cvs subversion automatically merge updating dvcses make distinction fetching new content merging workspace already described normally combine operations others tend ask user hand provide ways send shiver pythonic spine another one git mercurial clone replicates repo checkout switches branches single workspace bzr clone alias checkout normally creates new workspace obvious push changes back upstream important remember centralized systems like cvs subversion committing pushing dvcs operations separate many projects workflow record changes local repo push shared repo afaik contenders call record operation commit publish operation push1 workflows hear based mailing patches eg linux yet others based gatekeepers pulling repo arch developers tend favor dont worry going relevant python participating developers point view eric raymonds inprogress survey captures aspect pretty well distinction update record merge record terms point cvs subversion commit mainline havent merged concurrent changes mainline distributed vcs hand record changes locally merge revisions convenience finally pushing upstream sound like small difference actually amazingly liberating otherwise doesnt need different current workflow doubt active python developers start feel need seems potential leading anarchy git designed around linuss ability manage chaos linus anarchy true python although personalities leading developers different details anarchy differ optimistic way put point dvcses great potential encouraging experimentation general youll always pretty good idea want pull gatekeepers tell may push footnotes 1 darcs uses record record operation darcs highly unlikely become python dvcs choice _______________________________________________ pythondev mailing list zvlllneumpythonorg httpmailpythonorgmailmanlistinfopythondev unsubscribe httpmailpythonorgmailmanoptionspythondevpythondev40tangomucom thu 07 aug 2008 043854 0900 pythondev primer distributed revision control