Hi John, On Sun, Apr 4, 2010 at 2:59 AM, John Cremona <[email protected]> wrote: > I'm updating the files in data/extcode/pari/simon/ in order to deal > with #6955 and #5153. My patch will update the Sage library files, > but how can I make a patch to change those files (which are not under > hg control)?
I think everything under the directory SAGE_ROOT/data/extcode/ is under the control of Mercurial. However, the directory SAGE_ROOT/data/ is not under revision control. For example, [mv...@sage data]$ pwd /dev/shm/mvngu/sandbox/sage-4.3.5/data [mv...@sage data]$ hg status abort: There is no Mercurial repository here (.hg not found)! [mv...@sage data]$ cd extcode/ [mv...@sage extcode]$ hg status <NO-OUTPUT> > Do I just attach the (3) changed files to the ticket? The current situation is this. Everything under the directory SAGE_ROOT/data/extcode/ is a Mercurial repository called extcode-main. And everything under SAGE_ROOT/devel/sage-main/ is a Mercurial repository called sage-main. For a list of all known Sage Mercurial repositories, see the Mercurial repositories page [1]. To make changes to extcode-main and sage-main, you need to upload to trac separate patches to those two repositories. The same thing applies if you wanted to make changes to the scripts repository under SAGE_ROOT/local/bin/ as well as changes to the Sage library. [1] http://hg.sagemath.org -- Regards Minh Van Nguyen -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org To unsubscribe, reply using "remove me" as the subject.
