diff options
| author | Junio C Hamano <gitster@pobox.com> | 2023-04-17 21:55:35 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2023-04-17 21:55:35 -0700 |
| commit | 4304bf6b4ee4210f0aee438088114a7761d2d667 (patch) | |
| tree | 7d2620971a1ac9f05d6b6ff6a1d51755287f8a4d /MyFirstContribution.txt | |
| parent | 3a9663e144bda415dcecea9f62d6da4e5affe0de (diff) | |
| download | git-htmldocs-4304bf6b4ee4210f0aee438088114a7761d2d667.tar.gz | |
Autogenerated HTML docs for v2.40.0-352-g667fc
Diffstat (limited to 'MyFirstContribution.txt')
| -rw-r--r-- | MyFirstContribution.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/MyFirstContribution.txt b/MyFirstContribution.txt index 2f8b7d597..56130e4be 100644 --- a/MyFirstContribution.txt +++ b/MyFirstContribution.txt @@ -1164,7 +1164,7 @@ After you run this command, `format-patch` will output the patches to the `psuh/ 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 -"psuh/v2-*.patch" (not "psuh/*.patch", which would match v1 and v2 patches). +`psuh/v2-*.patch` (not `psuh/*.patch`, which would match v1 and v2 patches). Edit your cover letter again. Now is a good time to mention what's different between your last version and now, if it's something significant. You do not |