Databases
StackOverflow2013
Postsdbo
POHow to swap Mercurial Queues in and out of a repository
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to swap Mercurial Queues in and out of a repository
    text
    copied!<p>I have a platform neutral mercurial code repo called "Simulator"</p> <p>and want to apply patches that target specific platform's optimizations before a build. </p> <p>According to the guide we can accomplish this by the use of patches with guards.</p> <ul> <li>Windows Experimental.patch +windows</li> <li>Unix Experimental.patch +unix</li> <li>Mac Experimental.patch +mac</li> </ul> <p>However its starting to get cumbersome because our patch queue contains 100+ patches named like windows-memory-optimization.patch +windows, unix-memory-optimization.patch +unix, windows-io-experimental-bug-fix.patch +windows, etc etc. We organized it as groups in the series file, but the file is getting huge and using qseries / qapplied is getting unmanageable</p> <p>Instead we would like to have a queue for windows, unix and mac.</p> <p>So that patches can be organized as:</p> <ul> <li>Windows Patch Stack: memory-opt.patch, io-opt.patch, etc</li> <li>Unix Patch Stack: disk.patch, graphics.patch, etc </li> <li>Mac Patch Stack: io-fix.patch, io-opt.patch, experimental.patch, etc</li> </ul> <p>Then swap the patch stacks for each platform in and out of the simulator repo. So that I can work on the windows patch stack and pop/push various subsystem optimization patches and work on them independently of the unix or mac patch stacks.</p> <p>It does not look like I can do that, other than making 3 different repos specific to the each platform and maintaining the patch stacks that way. </p> <p>Is there a way to, other than manually copying the .hg/patches directory in and out of the repo, to accomplish "swapping" patch stacks?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload