#10190: developer's guide: new chapter "Advanced Mercurial Usage"
-------------------------------+--------------------------------------------
Reporter: mvngu | Owner: mvngu
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-4.6.1
Component: documentation | Keywords: Mercurial, developer's guide
Author: Minh Van Nguyen | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-------------------------------+--------------------------------------------
Comment(by rbeezer):
Replying to [comment:7 mvngu]:
> The above reviews by leif and rbeezer
Hi Minh and Leif,
I don't do as much system/build level work as leif, so his comments about
spkgs, etc are important. However this changes, linking back to any
advanced section is one way to keep the introduction short and make
everything available to the person with more experience, or the newcomer
who gains more experience.
When I start with newcomers (I've done this at least four times now), I
just do queues and we never invoke the editor. But I like Leif's
suggestion of including the editor command set up for vi and a comment in
the template about making a change as an option.
I've had at least one suggestion from an experienced developer to make
queues more prominent in the introduction and de-emphasise clones. I
struggled with clones whenever I had to update a patch or wanted to add a
reviewer patch, and I became so much more productive with queues. I don't
think they are hard, or advanced. Being optional does not necessarily
equate to being advanced.
There are two things I'd like to do long-term. A cleaner split between
clones and queues, maybe even rearranging the order. I'd also like to do
"queues under the hood" - a small discussion about the contents of
{{{.hg/patches}}} as a way of understanding what is really happening. Of
course that can all wait.
In a day or two I'll be totally busy with other stuff for a few weeks,
even 100% offline for a week. Feel free to pester me about a review if it
slips my mind once I'm back in the saddle (presuming no action in the next
day or two).
Rob
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10190#comment:8>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
