Sorry for following up to myself, but this typo might be very confusing: Stephen J. Turnbull writes: > Barry Warsaw writes: > > > You can have "co-located" branches[1] which essentially switch > > in-place, so if a branch is changing some .c files, you won't have > > to rebuild the whole world just to try out a patch. > > In Mercurial these are called "named branches", and they are > repo-local (by which I mean they must be part of the DAG). Named > branches used to have some inconvenient aspects relevant to standalone
s/relevant/relative/ > branches (they could be fairly confusing to other users if pushed > before being merge to mainline). > > It's not obvious to me that Mercurial style named branches would work > well here ... it would take a little thought to design an appropriate > workflow, anyway. > _______________________________________________ > 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/stephen%40xemacs.org _______________________________________________ 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
