mercurial-queue

问题 This is a best practice question, and I expect the answer to be "it depends". I just hope to learn more real world scenarios and workflows. First of all, I'm talking about different changes for the same project, so no subrepo please. Let's say you have your code base in an hg repository. You start to work on a complicated new feature A, then a complicated bug B is reported by your trusted tester (you have testers, right?). It's trivial if (the fix for) B depends on A. You simlply ci A then ci

问题 I just started using Git alongside Mercurial to familiarize myself with Git. I use the mq extension in Mercurial extensively to manage local patches, and I'm looking for a Git equivalent. Should I just use Git branch? Or are there better ways to manage local patches that enable easily applying and removing the patches? Thanks, 回答1: Check out "Patch-management Interface layers" section of Interfaces, Frontends And Tools page on Git Wiki. There are listed two patch management interfaces,