Mercurial: What is the benefit of fixing errors in earlier versions
Posted
by Ken Earley
on Stack Overflow
See other posts from Stack Overflow
or by Ken Earley
Published on 2010-04-23T12:41:23Z
Indexed on
2010/04/23
13:03 UTC
Read the original article
Hit count: 309
According to the guide, under the heading: Fixing errors in earlier revisions, it states this:
When you find a bug in some earlier revision you have two options: either you can fix it in the current code, or you can go back in history and fix the code exactly where you did it, which creates a cleaner history.
- How does going back in history make it cleaner? It still makes a new changeset at tip.
- Does it have something to do with what is recorded as it's parent?
- Is there a way to view the logs seeing the newly inserted changeset in that order?
- This lesson is under the main heading of Lone developer with nonlinear history. Is this good practice when working on a team?
© Stack Overflow or respective owner