#10190: developer's guide: warnings & notes about commit message, cloning and
setting the text editor
-------------------------------+--------------------------------------------
Reporter: mvngu | Owner: mvngu
Type: enhancement | Status: needs_review
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:10 mvngu]:
Hi Minh,
Thanks for your work on this one. Two quick comments before I head out
for a bit.
1. When you say:
{{{
i.e. Mercurial queues, for efficiently working with a sandbox of
the Sage library
}}}
I think it would be better not to infer that queues give you a "sandbox".
A clone makes a copy of lots of source code and if you wreck it you can
delete it. No harm. Queues work on the one copy of source code, though
it is easy to back out of a mess, but you can't just trash it. Maybe
delete "a sandbox of" for each copy of the warning?
2. I think leif's suggestion was to put an "editor=" line in the
template, all filled in to point to vim. I have new users cut/paste the
template to construct an {{{.hgrc}}} file - somebody wishing to change it
would find it later in their {{{.hgrc}}}.
Gotta run.
Rob
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10190#comment:11>
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.
