From: jas@corpus-callosum.com (Jeff Sickel)
Subject: [9fans] drawterm bug
Date: Tue, 22 Mar 2011 13:02:40 -0500 [thread overview]
Message-ID: <AD1AE740-C723-498C-87CB-3E1B4F3E11F9@corpus-callosum.com> (raw)
In-Reply-To: <e5c3d419cd3c2aa6c186aabc4902ab4f@ladd.quanstro.net>
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
next prev parent reply other threads:[~2011-03-22 18:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 15:36 erik quanstrom
2011-03-22 14:40 ` erik quanstrom
2011-03-22 17:40 ` erik quanstrom
2011-03-22 17:59 ` Skip Tavakkolian
2011-03-22 18:57 ` erik quanstrom
2011-03-22 17:45 ` Jeff Sickel
2011-03-22 17:51 ` erik quanstrom
2011-03-22 18:02 ` Jeff Sickel [this message]
2011-03-25 19:48 ` Ethan Grammatikidis
2011-03-25 20:09 ` dexen deVries
2011-03-25 21:00 ` Jeff Sickel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AD1AE740-C723-498C-87CB-3E1B4F3E11F9@corpus-callosum.com \
--to=jas@corpus-callosum.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).