Luke describes a nice methodology for using Mercurial as a way to track patches from a subversion checkout. This type of workflow stuff is very cool imo because it has the following:
- Shows a concrete example of how to use a not so trivia tool
- Works within constraints (in this example, playing with a subversion checkout)
- Fills a need (Managing non-trivial changes to a centralized SCM model without sending tons of commits)
