On May 26, 2010, at 11:55 AM, kcrisman wrote:
way around that. Personally, I would say anyone not using queues is
at
a disadvantage,
True.
and they're really easy to pick up (especially if
Not without having someone over your shoulder, which is why I still
don't/can't use them. (Maybe Rob and Jason will finally teach me when
they visit in June!).
Sure. For a single patch, do
hg qnew -f some_name # create a changeset
hg qref -e # refresh the patch, including the commit message, as many
times as you want
hg qfinish tip # turn the patch into an actual commit
What's the point with a single patch? I use a
combination of rollback and --no-commit for now.
For creating good commit messages. Also, they're handy if you want to
try something out and that you want to easily be able to revert.
Random remark: One reason why HG alone is much harder than in Sage is
that there is no tab completion of the various HG commands, no
interactive verbose help accessible as easily with a ?, etc. That has
saved me in hg_sage many, many times.
One note--you don't have to type the whole command, just enough to
make it unique. (Not as good as tab completion, but nice).
- Robert
--
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