Fossil SCM

Fix documentation typo.

drh 2020-08-08 17:18 trunk
Commit 08ab286028274cc64a4198a1fbe3eef3fe2985dfb72810503621a0774b75e31a
1 file changed +1 -1
+1 -1
--- www/gitusers.md
+++ www/gitusers.md
@@ -137,11 +137,11 @@
137137
[3]: ./rebaseharm.md
138138
139139
## Branch and Tag Names
140140
141141
Fossil has no special restrictions on the names of tags and branches,
142
-though you might want to to keep [Git's tag and branch name restrictions][4]
142
+though you might want to keep [Git's tag and branch name restrictions][4]
143143
in mind if you plan on mirroring your Fossil repository to GitHub.
144144
145145
[4]: https://git-scm.com/docs/git-check-ref-format
146146
147147
Fossil does not require tag and branch names to be unique. It is
148148
--- www/gitusers.md
+++ www/gitusers.md
@@ -137,11 +137,11 @@
137 [3]: ./rebaseharm.md
138
139 ## Branch and Tag Names
140
141 Fossil has no special restrictions on the names of tags and branches,
142 though you might want to to keep [Git's tag and branch name restrictions][4]
143 in mind if you plan on mirroring your Fossil repository to GitHub.
144
145 [4]: https://git-scm.com/docs/git-check-ref-format
146
147 Fossil does not require tag and branch names to be unique. It is
148
--- www/gitusers.md
+++ www/gitusers.md
@@ -137,11 +137,11 @@
137 [3]: ./rebaseharm.md
138
139 ## Branch and Tag Names
140
141 Fossil has no special restrictions on the names of tags and branches,
142 though you might want to keep [Git's tag and branch name restrictions][4]
143 in mind if you plan on mirroring your Fossil repository to GitHub.
144
145 [4]: https://git-scm.com/docs/git-check-ref-format
146
147 Fossil does not require tag and branch names to be unique. It is
148

Keyboard Shortcuts

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