Tres Seaver writes: > On 03/23/2011 01:24 PM, Antoine Pitrou wrote: > > On Wed, 23 Mar 2011 10:25:01 -0700 > > Ethan Furman <et...@stoneleaf.us> wrote: > >> > >> I think the use-case has been lost. Think sprints and multiple push > >> races.
I do, can't speak for others. So what? *sigh* ... read on. > > Well, keep in ming hg is a *distributed* version control system. You > > don't have to push your changes right now. s/push your changes right now/push your changes to the public repo/ > That doesn't work so well at a sprint, where the point is to maximize > the value of precious face-time to get stuff done *now*. That's where the D in DVCS comes in. It's a new world, friends. All you need to do is bring a $50 wireless router to the sprint, and have some volunteer set up a shared repo for the sprinters. Then some volunteer *later* runs the tests and pilots the patches into the public repo. Where's the latency? N.B. The repo admin and test-running volunteers can be non-coders. In fact, the tests can be running concurrently (gives those non-coders an excuse to attend sprints!), but nobody need wait for the results. > Maybe we need to chop the problem up as: "Violence is the last refuge of the incompetent." ObRef Asimov.<wink> _______________________________________________ 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
