On May 26, 8:34 pm, William Stein <wst...@gmail.com> wrote: > On Wed, May 26, 2010 at 5:31 PM, kcrisman <kcris...@gmail.com> wrote: > > >> > Not without having someone over your shoulder, which is why I still > >> > don't/can't use them. (Maybe Rob and Jason will finally teach me when > >> > they visit in June!). > > >> Sure. For a single patch, do > > >> hg qnew -f some_name # create a changeset > >> hg qref -e # refresh the patch, including the commit message, as many > >> times as you want > >> hg qfinish tip # turn the patch into an actual commit > > > I see. I guess for me I don't see the point of creating a new patch > > (again, for multiple strands I definitely see the point); I just wait > > until I'm done. Already my eyes glaze over ... :) But, like I said, > > Jason now has to promise to give me an in-person tutorial after fried > > clams! > > >> > What's the point with a single patch? I use a > >> > combination of rollback and --no-commit for now. > > >> For creating good commit messages. Also, they're handy if you want to > >> try something out and that you want to easily be able to revert. > > > Again, hg_sage.rollback() and hg_sage.revert(options='--all') do that > > now for a single patch. > > > In fact, I should really make hg_sage.revert_all() as an alias for > > that. Is there a problem with adding new commands like that, or > > should we only stick to ones which are actual HG commands? > > Go for it! I wrote hg_sage in a big hurry, and had always expected > *YOU* were going to come along and greatly improve it, e.g., filling > out all the capabilities, adding full support for queues, etc. >
Just checking :) (But not necessarily for queues!) -- 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
