|
Size: 1033
Comment:
|
← Revision 14 as of 2009-05-19 19:31:00 ⇥
Size: 137
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| Email: [[MailTo(byteshack<-A-T->gmail<-D-O-T->com)]] | |
| Line 7: | Line 6: |
| === The mq extension === I'm very interested on what the mq extension does. I guess for me it is still a solution looking for a problem, and until I can't fully understand what the problem is, I wont enjoy and fully utilize the solution it provides. Hopefully I can put some stuff that I figure out here. |
|
| Line 10: | Line 7: |
| === Random hg use scenarios === Mercurial has a bit of a feature bloat. It is not bad, but it is just hard to know what everything does. There is a LOT of functionality all over the place. This is a place holder of pointer to stuff I seem to forget easily. |
= Mq Tutorial = |
| Line 13: | Line 9: |
| * Good repo layout? Seems to be a good idea to keep a couple of repos around: upstream, localchanges, outbound. upstream should be kept sync'd with the source, and not modified at all. * To see changes comming from upstream into one of your local repos do: {{{ $ cd localrepo $ hg incoming }}} |
Moved to MqTutorial |
