diff options
| author | Elijah Newren <newren@gmail.com> | 2023-10-08 06:45:20 +0000 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2023-10-09 12:06:29 -0700 |
| commit | 9a9fd289cc81a3bb69eb2b4e11db27509e0eb515 (patch) | |
| tree | 613ec5217e16120fa374f5c60cc815db770e0245 /Documentation/SubmittingPatches | |
| parent | 0cac690e1ac5e26ecf2dba0c53ac3824425446b5 (diff) | |
| download | git-9a9fd289cc81a3bb69eb2b4e11db27509e0eb515.tar.gz | |
documentation: use clearer prepositions
Diff best viewed with --color-diff.
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/SubmittingPatches')
| -rw-r--r-- | Documentation/SubmittingPatches | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 973d7a81d4..0e2d3fbb9c 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -87,7 +87,7 @@ maintainer. Under truly exceptional circumstances where you absolutely must depend on a select few topic branches that are already in `next` but not in `master`, you may want to create your own custom base-branch by forking -`master` and merging the required topic branches to it. You could then +`master` and merging the required topic branches into it. You could then work on top of this base-branch. But keep in mind that this base-branch would only be known privately to you. So when you are ready to send your patches to the list, be sure to communicate how you created it in |