diff options
| author | Junio C Hamano <gitster@pobox.com> | 2022-09-21 15:47:52 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2022-09-21 15:47:52 -0700 |
| commit | a1ee129f6273b4bebf20726604a5f9eeb873ffa9 (patch) | |
| tree | 924dc36d5040f88b1d3797c823686e35e290926b /MyFirstContribution.html | |
| parent | bb778e77f3ba317e02d2880ca7148ea66a17dd8a (diff) | |
| download | git-htmldocs-a1ee129f6273b4bebf20726604a5f9eeb873ffa9.tar.gz | |
Autogenerated HTML docs for v2.38.0-rc1
Diffstat (limited to 'MyFirstContribution.html')
| -rw-r--r-- | MyFirstContribution.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/MyFirstContribution.html b/MyFirstContribution.html index 5b18b97a1..1d0668361 100644 --- a/MyFirstContribution.html +++ b/MyFirstContribution.html @@ -1880,7 +1880,7 @@ as version "2". For instance, you may notice that your v2 patches are all named like <code>v2-000n-my-commit-subject.patch</code>. <code>-v2</code> will also format
your patches by prefixing them with "[PATCH v2]" instead of "[PATCH]",
and your range-diff will be prefaced with "Range-diff against v1".</p></div>
-<div class="paragraph"><p>Afer you run this command, <code>format-patch</code> will output the patches to the <code>psuh/</code>
+<div class="paragraph"><p>After you run this command, <code>format-patch</code> will output the patches to the <code>psuh/</code>
directory, alongside the v1 patches. Using a single directory makes it easy to
refer to the old v1 patches while proofreading the v2 patches, but you will need
to be careful to send out only the v2 patches. We will use a pattern like
@@ -2060,7 +2060,7 @@ should generate your diffs from <code><topic>..<mybranch></code> and <div id="footer">
<div id="footer-text">
Last updated
- 2022-05-25 17:44:40 PDT
+ 2022-09-21 15:44:34 PDT
</div>
</div>
</body>
|