Fossil SCM

Fix a typo in the rebaseharm.md document.

drh 2019-09-06 14:39 trunk
Commit 82f75864d5664a1ea7c9a9d6f258f8c733313883c0066736b8cc81f74824ca1e
1 file changed +1 -1
--- www/rebaseharm.md
+++ www/rebaseharm.md
@@ -203,11 +203,11 @@
203203
of Git. Wouldn't it be better to fix the tool rather than to lie about
204204
the project history?
205205
206206
## 7.0 Cherry-pick merges work better then rebase
207207
208
-Perhaps there some cases where a rebase-like transformation
208
+Perhaps there are some cases where a rebase-like transformation
209209
is actually helpful. But those cases are rare. And when they do
210210
come up, running a series of cherry-pick merges achieve the same
211211
topology, but with advantages:
212212
213213
1. Cherry-pick merges preserve an honest record of history.
214214
--- www/rebaseharm.md
+++ www/rebaseharm.md
@@ -203,11 +203,11 @@
203 of Git. Wouldn't it be better to fix the tool rather than to lie about
204 the project history?
205
206 ## 7.0 Cherry-pick merges work better then rebase
207
208 Perhaps there some cases where a rebase-like transformation
209 is actually helpful. But those cases are rare. And when they do
210 come up, running a series of cherry-pick merges achieve the same
211 topology, but with advantages:
212
213 1. Cherry-pick merges preserve an honest record of history.
214
--- www/rebaseharm.md
+++ www/rebaseharm.md
@@ -203,11 +203,11 @@
203 of Git. Wouldn't it be better to fix the tool rather than to lie about
204 the project history?
205
206 ## 7.0 Cherry-pick merges work better then rebase
207
208 Perhaps there are some cases where a rebase-like transformation
209 is actually helpful. But those cases are rare. And when they do
210 come up, running a series of cherry-pick merges achieve the same
211 topology, but with advantages:
212
213 1. Cherry-pick merges preserve an honest record of history.
214

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button