Hi Mariah,

On Wed, Sep 16, 2009 at 11:10 PM, Mariah <mariah.le...@gmail.com> wrote:

<SNIP>

> What I do not know how to do is to indicate that this is for the file
>
>  sage-4.1.1/sage/misc/misc.py
>
> in
>
>  spkg/standard/sage-4.1.1.spkg
>
> Is there a convention as to how to indicate this?

Do you mean producing a proper patch file using Mercurial? If yes,
then you can use the Mercurial that's shipped with Sage like so. From
SAGE_ROOT, you can do something along the lines of the following
terminal session:

[mv...@sage sage-4.1.1-sage.math]$ ./sage
----------------------------------------------------------------------
| Sage Version 4.1.1, Release Date: 2009-08-14                       |
| Type notebook() for the GUI, and license() for information.        |
----------------------------------------------------------------------
sage: !bash
[mv...@sage sage-4.1.1-sage.math]$ cd devel/sage-main/
[mv...@sage sage-main]$ emacs sage/misc/misc.py

# or use your favourite editor to make changes to that misc.py file

[mv...@sage sage-main]$ hg ci  # now check in your changes
No username found, using 'mv...@sage.math.washington.edu' instead
[mv...@sage sage-main]$ hg export tip > ~/mypatch.patch
[mv...@sage sage-main]$ exit
exit
sage: exit

And upload that file ~/mypatch.patch to the trac server or send the
patch to sage-support. Either way is OK.

-- 
Regards
Minh Van Nguyen

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to 
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to