Excerpts from Tony Mechelynck's message of Wed Jul 17 03:45:35 +0200 2013: > You can share them in diff format, just like the patches that I see on > vim_dev. I'm talking about "hg pull" like sharing.
> URL? still the same: http://vim-wiki.mawercer.de/wiki/vim-development/development.html The script below shows how you can have a topic branch, merge "default" into it by "hg pmerge", and still pull/push it. Try the same with mq, you'll end up in a mess (with distributed development) That's the main difference. Person B can fix bugs in the topic branch of Person A. Person C can develop a feature on top of that topic branch etc. Whether this is useful depneds on the use case - but you can push to bitbucket or the like. Marc Weber rm -fr test ( set -x set -e mkdir -p test/source add_commit(){ echo $1 > $1 hg add $1 hg commit -m $1 } ( cd test/source hg init . add_commit a hg pnew -t topic-msg topic # this will not show up, because its committed upstream below, see [up] add_commit topic-commit-1 # these will end up in the topic diff add_commit topic-commit-2 ) # clone topic hg clone test/source test/clone ( cd test/source hg update -C default add_commit upstream-change # let's make it more complicated, feed topic-commit upstream [up] add_commit topic-commit-1 # add a third topic change: hg update -C topic add_commit topic-commit-3 ) ( cd test/clone # now get updates of the topic branch by pull # and this is what I don't like, you cannot "preview" using mercurial .. # best you could do is make a backup of this repo before pulling .. # so this should get topic-commit-3 into the clone hg pull -u hg update -C default add_commit last hg update -C topic # merge this patch upstream hg pmerge # and this is the cool thing, you can just push the updated topic without # "diff" formats: hg push -b topic ../source ) ( # export (we don't have deps, but this would export topics on which this topic depneds, too) cd test/source hg update -C topic hg pexport -U 10 ) ) -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
