I just built a clone in about a minute. On a fresh install of
4.5.2.rc0 created from source. Maybe with a binary install, the docs
need to be built on the first clone? Maybe a second clone would
happen without the documentation being built?
For the uninitiated or timid,
(a) making a clone
followed by
(b) hg_sage.{apply, commit/export}
are quick "safe" ways to review a patch, or create a simple patch. Or
a clone is a simple way to make a place to fiddle with the code. The
trouble comes when a submitted patch needs revision, or a reviewed
patch needs additions from a reviewer, etc. I have showed a couple of
people how to use queues in person and it takes about three hours to
go through the whole process of making a patch when they start with
zero experience with Sage source code. So it is not a trivial thing
to understand.
Long-term, I agree that queues are the best way to go. I wrote the
"Developer Walkthrough" with the idea that it would make it easier for
folks to get started with Sage development. Some basic ideas are
mixed into the first discussion about clones, so it would not be easy
to just make the clone material come after the queue material. But I
am open to any suggestions on how to improve that material and willing
to rehabilitate it.
Rob
--
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
