Fossil SCM
Removed a repeated word in fossil-v-git
Commit
b798e89a7eb3e2631ee7410ac5626a75d578ed0428f3e165c3ec088cb1e9e49a
Parent
73381119d8283e5…
1 file changed
+1
-1
+1
-1
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -213,11 +213,11 @@ | ||
| 213 | 213 | normally syncs immediately to its parent repository, so that |
| 214 | 214 | explicit pushes are not needed.</p></li> |
| 215 | 215 | |
| 216 | 216 | <li><p><b>Branch names sync:</b> Unlike in Git, branch names are not |
| 217 | 217 | purely local labels. They sync along with everything else, so |
| 218 | - everyone everyone sees the same set of branch names.</p></li> | |
| 218 | + everyone sees the same set of branch names.</p></li> | |
| 219 | 219 | |
| 220 | 220 | <li><p><b>Private branches are rare:</b> |
| 221 | 221 | [/doc/trunk/www/private.wiki|Private branches exist in Fossil], but |
| 222 | 222 | they're normally used to handle rare exception cases, whereas in |
| 223 | 223 | many Git projects, they're part of the straight-line development |
| 224 | 224 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -213,11 +213,11 @@ | |
| 213 | normally syncs immediately to its parent repository, so that |
| 214 | explicit pushes are not needed.</p></li> |
| 215 | |
| 216 | <li><p><b>Branch names sync:</b> Unlike in Git, branch names are not |
| 217 | purely local labels. They sync along with everything else, so |
| 218 | everyone everyone sees the same set of branch names.</p></li> |
| 219 | |
| 220 | <li><p><b>Private branches are rare:</b> |
| 221 | [/doc/trunk/www/private.wiki|Private branches exist in Fossil], but |
| 222 | they're normally used to handle rare exception cases, whereas in |
| 223 | many Git projects, they're part of the straight-line development |
| 224 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -213,11 +213,11 @@ | |
| 213 | normally syncs immediately to its parent repository, so that |
| 214 | explicit pushes are not needed.</p></li> |
| 215 | |
| 216 | <li><p><b>Branch names sync:</b> Unlike in Git, branch names are not |
| 217 | purely local labels. They sync along with everything else, so |
| 218 | everyone sees the same set of branch names.</p></li> |
| 219 | |
| 220 | <li><p><b>Private branches are rare:</b> |
| 221 | [/doc/trunk/www/private.wiki|Private branches exist in Fossil], but |
| 222 | they're normally used to handle rare exception cases, whereas in |
| 223 | many Git projects, they're part of the straight-line development |
| 224 |