Skip to content

Commit 6c6149a

Browse files
committed
Use <code> tag instead of deprecated <tt>
1 parent 32cb86c commit 6c6149a

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

index.html

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -108,11 +108,11 @@ <h2>How can you use GitGitGadget?</h2>
108108
You might also want to read the <a href="https://git-scm.com/docs/gitworkflows">gitworkflows</a> manual page to understand how your contributions will be integrated in Git's repository, as well as <a href="https://github.com/git/git/blob/todo/MaintNotes">this note from Git's maintainer</a>.
109109
</p><p>
110110
The first time you use GitGitGadget, you need to be added to the list of users with permission to use GitGitGadget (this is a <i>very</i> simple anti-spam measure).
111-
Any user who is already on that list can do that, by adding a comment to that Pull Request that says <tt>/allow &lt;username&gt;</name></tt> (with your GitHub login name).
111+
Any user who is already on that list can do that, by adding a comment to that Pull Request that says <code>/allow &lt;username&gt;</name></code> (with your GitHub login name).
112112
</p><p>
113113
The Pull Request will trigger a few Checks, most importantly one that will build Git and run the test suite on the main platforms, to make sure that everything works as advertised.
114114
</p><p>
115-
Once everything is ready to go, add a comment to that Pull Request saying <tt>/submit</tt>.
115+
Once everything is ready to go, add a comment to that Pull Request saying <code>/submit</code>.
116116
This will trigger GitGitGadget (you can see the progress via the Check called "GitGitGadget PR Handler"): it will wrap your Pull Request into a nice bundle of mails in the format expected on the Git mailing list.
117117
</p>
118118
</div>
@@ -124,7 +124,7 @@ <h2>What happens after GitGitGadget sent the mails?</h2>
124124
The Git developer community is globally distributed, so please wait a day or two for reviewer comments to trickle in before sending another iteration of your patch series (if needed).
125125
</p><p>
126126
In the case that a reviewer asks for changes, you should respond either acknowledging that you will make those changes or making an argument against the requested changes.
127-
If your patches need to be revised, please use <tt>git rebase -i</tt> to do that, then force-push, then update the description of the Pull Request by adding a summary of the changes you made, and then issue another <tt>/submit</tt>.
127+
If your patches need to be revised, please use <code>git rebase -i</code> to do that, then force-push, then update the description of the Pull Request by adding a summary of the changes you made, and then issue another <code>/submit</code>.
128128
</p>
129129
</div>
130130

@@ -161,22 +161,22 @@ <h2>Should I use GitGitGadget on GitGitGadget's Git fork or on Git's GitHub mirr
161161
<td class="tg-baqh"></td>
162162
</tr>
163163
<tr>
164-
<td class="tg-0lax">Comment on the PR when the series is integrated into <tt>pu</tt>, <tt>next</tt>, <tt>master</tt> and <tt>maint</tt></td>
164+
<td class="tg-0lax">Comment on the PR when the series is integrated into <code>pu</code>, <code>next</code>, <code>master</code> and <code>maint</code></td>
165165
<td class="tg-baqh"></td>
166166
<td class="tg-baqh"></td>
167167
</tr>
168168
<tr>
169-
<td class="tg-0lax">Add a label to the PR when the series is integrated into <tt>pu</tt>, <tt>next</tt>, <tt>master</tt> and <tt>maint</tt></td>
169+
<td class="tg-0lax">Add a label to the PR when the series is integrated into <code>pu</code>, <code>next</code>, <code>master</code> and <code>maint</code></td>
170170
<td class="tg-baqh"></td>
171171
<td class="tg-baqh"></td>
172172
</tr>
173173
<tr>
174-
<td class="tg-0lax">Target <tt>pu</tt>, <tt>next</tt>, <tt>master</tt> and <tt>maint</tt></td>
174+
<td class="tg-0lax">Target <code>pu</code>, <code>next</code>, <code>master</code> and <code>maint</code></td>
175175
<td class="tg-baqh"></td>
176176
<td class="tg-baqh"></td>
177177
</tr>
178178
<tr>
179-
<td class="tg-0lax">Target any topic branch in the maintainer's fork, as well as <tt>git-gui/master</tt></td>
179+
<td class="tg-0lax">Target any topic branch in the maintainer's fork, as well as <code>git-gui/master</code></td>
180180
<td class="tg-baqh"></td>
181181
<td class="tg-baqh"></td>
182182
</tr>

0 commit comments

Comments
 (0)