Difference between revisions of "Managing Local Changes with Mercurial Queues"

From gem5
Jump to: navigation, search
Line 2: Line 2:
 
gem5 users typically opt to freeze their repository at a particular changeset when starting a new research project. This approach has several downsides:
 
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.
+
* 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 useful change is added to the source tree, it's a long, tedious process to update.
  
 
== Mercurial Queues ==
 
== Mercurial Queues ==

Revision as of 17:37, 16 February 2013

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.

Mercurial Queues