From mboxrd@z Thu Jan 1 00:00:00 1970 From: jas@corpus-callosum.com (Jeff Sickel) Date: Tue, 22 Mar 2011 13:02:40 -0500 Subject: [9fans] drawterm bug In-Reply-To: References: <6a7e42f7236652d4761e22c1159e92db@ladd.quanstro.net> <6223ef47198082d6b74693b16a82846b@ladd.quanstro.net> Message-ID: Topicbox-Message-UUID: bea97764-ead6-11e9-9d60-3106f5b1d025 On Mar 22, 2011, at 12:51 PM, erik quanstrom wrote: >> back in the right order. Needs work, well, time, it takes time. > > hey, wait a second ... i thought that was the whole point of hg, > to save time. :-) It does, as long as you don't use certain extensions. > there were some definate gotchas > - hg diff doesn't do the right thing with a patch queue. > - hg qpush is terribly misnamed; and hg push --mq is just a poke in the eye. > - bitbucket tracks qupdate not qcommit. i don't understand this. Cloning and not using quilted patch queues does man you can work along in your branch of code as needed. Flush out a change, diff it w/ someone other revision/tip/repository and go to town. Export the changes upstream and it is a bit easier, even push them. I've just not taken the time to fully grok the way Bitbucket and a few others use mq. Too much complexity triggers the trap. -jas