As a follow-up to talking about queues at SD7, here are a few things I forgot to mention, for those that are interested:
0. For those interested in more, see http://hgbook.red-bean.com/hgbook.html ( http://hgbook.red-bean.com/ for other formats). 1. treat "hg qrefresh" and "hg qnew" as a commit command. That means that if you create a new file, you must first "hg add" the file and then "hg qrefresh" or "hg qnew -f" to pick up the new file. I believe the same applies to deleting a file. Thanks to roed for bringing issue up. 2. One very cool advanced thing you can do with queues is have a repository for your patches. That means you and several other people can version-control your patches (separately from the main repository), snapshot and rollback your patches to previous versions, etc. For more information, see http://hgbook.red-bean.com/hgbookch12.html#x16-29200012.11 The basic idea is that you run "hg init" in your .hg/patches directory (or when you initialize the patches, do it with "hg qinit -c"). You have the full power of mercurial with this, including pushing and pulling patches to other people. See also the qcommit command. 3. To import a patch (e.g., a patch on trac), do "hg qimport". This basically just copies the patch file to your .hg/patches directory and adds it the series file, but doesn't apply the patch. You'll have to hg qpush to apply the patch. 4. To break a bundle up into patches from the command line, do: hg incoming -p bundle-file-name.hg from within your repository. Robert said that this was how he implemented the bundle viewing on trac (thanks to Robert for this tip) Thanks, Jason --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@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-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
