On Feb 9, 11:15 am, John Cremona <john.crem...@gmail.com> wrote: > People are answering the question I intended to ask. So far no-one > uses the branching mechanism. Who knows if it still works....if it > doesn't someone should remove mention of it from the docs.
Oh, it works, or at least has within the last year. I think it's great that we've made the updates to the developer guide that explain queues, and I have been using them a lot more for the last year or so. But remember, a lot of the infrastructure was put in place in order to aid new developers who known *nothing* about branches, git, revision control, anything. For this sort of newcomer, having all tools available as "close to home" as possible - like "sage -clone" - lowers the learning curve enough that they might want to learn enough to be more efficient. If you want to make more than one patch, or apply a patch and then write a reviewer patch, going back to an "untouched" Sage is hard without using queues or cloning. I'm *not* suggesting that we should tell everyone to go back to branches, and could even de-emphasize this. (The developer guide could have a "What if I have no idea what you are talking about, but want to contribute anyway" section that preserves a lot of the 'newbie' stuff, for instance.) But having that extra help at the beginning - especially for those who don't get introduced to Sage development with people by their side - is worth preserving. - kcrisman -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
