Hi:
Suppose you follow the instructions in the programming
manual to edit one of the latex doc files, such as prog,tex,
const.tex, tut.tex, etc.
http://www.sagemath.org/doc/html/prog/node31.html
Roughly, the steps are
sage: hg_doc.pull()
(edit the file, say devel/doc/prog.tex)
sage: hg_doc.commit()
sage: hg_doc.send('prog20070118.hg')
Now suppose you decide to do more editing
and create a new patch bundle. It has been my
experience that if you do that the diff file which
hg_doc.commit displays will only show
the most recent edits. If that is the desired behavior,
what is the simplest way to "start from scratch"
(short of starting over again on a completely different
copy of sage)? With src patches, you simply can start
a new clone. That trick does not seem to work for hg_doc.
- David Joyner
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~----------~----~----~----~------~----~------~--~---
