diff options
author | Junio C Hamano <gitster@pobox.com> | 2023-10-23 14:45:54 -0700 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2023-10-23 14:45:54 -0700 |
commit | 33be82183d4cd6dc645f64da1402cf9a3f4cdbf3 (patch) | |
tree | 4a681cad5c6da23a7d7f56022666fb31397026d2 /SubmittingPatches.html | |
parent | 359f02427091f2c0fcac4eb7651fe5d159b84a54 (diff) | |
download | git-htmldocs-33be82183d4cd6dc645f64da1402cf9a3f4cdbf3.tar.gz |
Autogenerated HTML docs for v2.42.0-482-g2e8e7
Diffstat (limited to 'SubmittingPatches.html')
-rw-r--r-- | SubmittingPatches.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/SubmittingPatches.html b/SubmittingPatches.html index cda99ae6d..8bbe2ecf3 100644 --- a/SubmittingPatches.html +++ b/SubmittingPatches.html @@ -735,7 +735,7 @@ asciidoc.install(); <body class="article">
<div id="header">
<h1>Submitting Patches</h1>
-<span id="revdate">2023-10-20</span>
+<span id="revdate">2023-10-23</span>
</div>
<div id="content">
<div class="sect1">
@@ -846,7 +846,7 @@ maintainer.</p></div> <div class="paragraph"><p>Under truly exceptional circumstances where you absolutely must depend
on a select few topic branches that are already in <code>next</code> but not in
<code>master</code>, you may want to create your own custom base-branch by forking
-<code>master</code> and merging the required topic branches to it. You could then
+<code>master</code> 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
@@ -1518,7 +1518,7 @@ this problem around.</p></div> <div id="footer">
<div id="footer-text">
Last updated
- 2023-08-21 10:25:10 PDT
+ 2023-10-23 14:43:47 PDT
</div>
</div>
</body>
|