Mercurial queues are great, as I am just beginning to see. Thanks for sharing.
Dmitrii On Feb 4, 3:03 am, bump <b...@match.stanford.edu> wrote: > > make a new patch replacing the present one? > > --- I have trouble understanding how to do this in mercurial. > > Do I backout my previous patch and make a new one? (I tried this > > and it didn't seem to work. If anyone knows > > how to do this exactly, I'd most appreciate hearing details or being > > pointed to a readable manual/howto...) > > It's a good idea to use a mercurial queues, which bring sanity to > working on patches. > > Mercurial queues are explained in O'Sullivan's book, which are > online:http://hgbook.red-bean.com/ > as well as the doc patches in #8108 and #8147. > > But to get started, clone sage: > > $ sage -clone work > > This will create a subdirectory of the sage root directory called > devel/sage-work. Here $ is command line prompt. > > In the directory devel/sage-work you can start a mercurial queue with > the command > $ hg qinit -c > > Then you can start a new patch with the command $ hg qnew > or you can import an existing patch that you want to work on with $ hg > qimport [patchname]. > > The patches are in the directory devel/sage-work/.hg/patches . > > Dan -- 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
