Skip to main content
Post Made Community Wiki
Explained the questioner's problem as the tangled working copy problem.
Source Link
jammycakes
  • 1.2k
  • 1
  • 11
  • 10

The Single Responsibility Principle.

Every source control commit should serve only one purpose. If you have to put the word "and" or "also" in your summary, you need to split it up.

You can do thisIt's very common to end up with lots of separate unrelated or semi-related changes in your working copy. This is called the "tangled working copy problem," and it's actually very hard to avoid even for disciplined developers. However, Git and Mercurial both give you tools to resolve it -- with git using gitgit add -p or with Mercurial using chunkchunk selection and Mercurial Queues in TortoiseHg respectively.

The Single Responsibility Principle.

Every source control commit should serve only one purpose. If you have to put the word "and" or "also" in your summary, you need to split it up.

You can do this with git using git add -p or with Mercurial using chunk selection and Mercurial Queues in TortoiseHg.

The Single Responsibility Principle.

Every source control commit should serve only one purpose. If you have to put the word "and" or "also" in your summary, you need to split it up.

It's very common to end up with lots of separate unrelated or semi-related changes in your working copy. This is called the "tangled working copy problem," and it's actually very hard to avoid even for disciplined developers. However, Git and Mercurial both give you tools to resolve it -- git add -p or chunk selection and Mercurial Queues in TortoiseHg respectively.

Source Link
jammycakes
  • 1.2k
  • 1
  • 11
  • 10

The Single Responsibility Principle.

Every source control commit should serve only one purpose. If you have to put the word "and" or "also" in your summary, you need to split it up.

You can do this with git using git add -p or with Mercurial using chunk selection and Mercurial Queues in TortoiseHg.