SubmittingPatches: de-emphasize branches as starting points
It could be that a suitable branch does not exist, so instead just use the phrase "starting point". Technically speaking the starting point would be a commit (not a branch) anyway. Helped-by: Junio C Hamano <gitster@pobox.com> Signed-off-by: Linus Arver <linusa@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Linus Arver committed
Jul 14, 2023 at 06:01 UTC
b5dbfe28a4eafc2c6c7f495983f141abcafafdfb
1 file changed
+4
-4
Documentation/SubmittingPatches
+4
-4
@@ -7,8 +7,8 @@ Here are some guidelines for contributing back to this
7
project. There is also a link:MyFirstContribution.html[step-by-step tutorial]
8
available which covers many of these same guidelines.
9
10
-[[base-branch]]
11
-=== Decide what to base your work on.
10
+[[choose-starting-point]]
11
+=== Choose a starting point.
12
13
In general, always base your work on the oldest branch that your
14
change is relevant to.
@@ -317,8 +317,8 @@ Please make sure your patch does not add commented out debugging code,
317
or include any extra files which do not relate to what your patch
318
is trying to achieve. Make sure to review
319
your patch after generating it, to ensure accuracy. Before
320
-sending out, please make sure it cleanly applies to the base you
321
-have chosen in the "Decide what to base your work on" section,
320
+sending out, please make sure it cleanly applies to the starting point you
321
+have chosen in the "Choose a starting point" section,
322
and unless it targets the `master` branch (which is the default),
323
mark your patches as such.
324