On Feb 21, 4:45 pm, "Johan S. R. Nielsen" <j.s.r.niel...@mat.dtu.dk> wrote: > I'm _only_ using queues at the moment. As far as I can see, clones are > neat if you have "projects" of patches. However, the beginner will not > usually have this but only a few scattered fixes here and there and > patches for review, with none or few dependencies between them. For > this, I think queues are much faster and lightweight. > I began with the clones just like the guide said, but found it > tiresome and switched to the queues as soon as I got to that part of > the guide. Also, clones are time consuming in the beginning when you > are anxious to just get started. I definitely don't think that they > should be part of the beginning of this walk-through. > I would use clones if I reviewed as many patches as I should; then I > would have a clone for my work (and patches that I need), and another > clone for the non-dependent set of patches I was currently reviewing. > However, I always have a clean, completely separate install of the > last stable release of Sage. I can't remember if that is mentioned in > the guide, but I find this helpful (and necessary) in a number of > ways. This only have the patches applied which I really need.
+1. Your experience is pretty much the same as mine was, when I first started poking around the Sage codebase. In fact, I think that queues would be easier on beginners than the cloning + commit/export cycle, rather than simply an efficiency boost, as they are currently portrayed in the Walking Through the Development Process article. It's much simpler to experiment and reverse your changes when you're using a patch queue than when you're committing to the main library history tree. I would propose to move the queues info up to the top of the page, maybe even earlier than the sections discussing branching. I also wonder why the development guide recommends that we use mercurial from inside a Sage session. It seems considerably more tedious than just using it from the command line. Is there some advantage I'm not seeing? By the way, Johan, by using `hg qqueues` you can easily keep one series for patches you need and one for patches you're reviewing - though it does take a bit longer to switch series and re-push patches than to just switch directories, of course. -Keshav -- 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
