Skip to content

Commit e6c7233

Browse files
committed
clarify giant commit use case
This is still somewhat hand-wavy though.
1 parent 5966d1a commit e6c7233

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

README.rst

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -138,8 +138,10 @@ bigger scale.
138138
Use case #4: Breaking down giant commits
139139
----------------------------------------
140140

141-
Split giant commit into commits one per hunk, then regroup into
142-
commits based on that.
141+
Split giant commit into commits one per hunk, then regroup into topics
142+
along with previous related commits. (Note that the previous related
143+
commits are required here for the regrouping to work, since hunks
144+
within a single commit are by definition independent of each other.)
143145

144146

145147
Installation

0 commit comments

Comments
 (0)