Managing Local Changes with Mercurial Queues

From gem5
Revision as of 13:39, 16 February 2013 by Atgutier (talk | contribs)
Jump to: navigation, search

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 any useful changes they may develop.
  • If a useful change is added to the source tree, it's a long, tedious process to update.

If a user chooses to keep their local repository up-to-date with the source tree they typically use named branches and merge any upstream changes into their branches.

Mercurial Queues