Stephen J. Turnbull wrote: > I don't know about svn; I find it pretty painful to use for anything > but sequential tasking (update ... hack ... commit ... repeat). But > if you look at http://git.kernel.org/, you'll see a thicket of repos, > each of which probably contains a few to a few hundred[1] branches > (mostly merged to repo mainline or abandoned, of course).
If it isn't already there, suspending work on something to work on something else would make a very nice scenario to cover, as it is something even the core devs sometimes have to deal with. I'd expect any DVCS to be able to handily beat what I currently do with SVN: - # hack on first task - svn diff > _patches/first_task.diff - svn revert -R . - svn update - # hack on second task - svn commit OR svn diff > _patches/second_task.diff (depending on whether or not I want it reviewed by someone else before committing it) - svn revert -R . - patch -p0 < _patches/first_task.diff - # back to hacking on first task Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --------------------------------------------------------------- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
