On Tue, Aug 3, 2010 at 12:22 AM, David Roe <[email protected]> wrote: > I use both clone and queues: if I'm working on multiple projects > simultaneously I would prefer to have a clone for each instead of just using > queues. This is especially important if some of my patches touch low level > .pxd files (e.g. sage/structure/element.pxd): I really don't want to be > pushing and popping that patch when I switch which project I'm working on. > David
This is how I work as well, and for the same reasons. It's also nice to have a clone to easily referee patches without disturbing what your'e currently working on. (Of course some people "clone" the entire Sage tarball rather than only the standard library, but that's too heavyweight for me...) Personally, I always kill the documentation build 'cause it takes way too long. If we need to do it on a clone (and I don't see why we would), could we at least do it in the background or on the first -docbuild? - Robert -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
