Managing Local Changes with Mercurial Queues
Repository Management Problem
gem5 users typically opt to freeze their repository at a particular changeset when starting a new research project. This approach has several downsides:
- It discourages users from contributing back useful changes.
- If a useful change is added to the source tree, it's a long, tedious process to update.