On Thu, Oct 02, 2008 at 03:21:41PM +0200, Guido G?nther wrote: > On Wed, Oct 01, 2008 at 10:46:41AM +0100, Daniel P. Berrange wrote: > [..snip..] > > Yep, as you say, there're two problems here. When creating the > > VM we need to make it clear which networks are active, and which > > are not - but still allow selection of an inactive network. > > > > When starting a VM, we need to check fi the network is active. If > > it is not, we should popup a confirmation dialog informing the > > user, and /asking/ if we should automatically start the network > > at this time. > Attached patch does just this - inactive networks are postfixed with > " (Inactive)" and when leaving the tab you're asked if you want to start > the newtork. > I'd split this into two but there doesn't seem to be a hg equivalient of > "git rebase -i; git reset HEAD^; git add -p" - so splitting patches is > much more cumbersome or am I missing something? I guess you're just doing commits straight ontop of a clone of the repo. If so I'd recommend using Mercurial's patch queue extension - it provides quilt-like functionality integrated into mercurial commands. I use it to maintain & rebase a long stack of patches - you can move up & down through the stack, rebasing at will, until you're ready to submit the patch, or formally commit it to the repository. Edit your $HOME/.hgrc and add [extensions] hgext.mq= Then you can do 'hg qinit' to start a queue, and 'hg qnew NAME' to create a new patch. You can do hg qnew multiple times to stack a series of patches, and 'hg qpop' / 'hg qpush' to move up & down through the stack, and 'hg qseries' to view the set. See 'hg help' for all the other useful commands - all prefixed with a 'q' Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/et-mgmt-tools
