SubmittingPatches: explain why 'next' and above are inappropriate base
The 'next' branch is primarily meant to be a testing ground to make sure that topics that are reasonably well done work well together. Building a new work on it would mean everything that was already in 'next' must have graduated to 'master' before the new work can also be merged to 'master', and that is why we do not encourage basing new work on 'next'. Helped-by: Linus Arver <linusa@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Jul 25, 2023 at 22:17 UTC
f835de52d7c36c278004383919c58457861dac6c
1 file changed
+8
-4
Documentation/SubmittingPatches
+8
-4
@@ -57,10 +57,14 @@ latest HEAD commit of `maint` or `master` based on the following cases:
57
58
This also means that `next` or `seen` are inappropriate starting points
59
for your work, if you want your work to have a realistic chance of
60
-graduating to `master`. They are simply not designed to provide a
61
-stable base for new work, because they are (by design) frequently
62
-re-integrated with incoming patches on the mailing list and force-pushed
63
-to replace previous versions of these branches.
60
+graduating to `master`. They are simply not designed to be used as a
61
+base for new work; they are only there to make sure that topics in
62
+flight work well together. This is why both `next` and `seen` are
63
+frequently re-integrated with incoming patches on the mailing list and
64
+force-pushed to replace previous versions of themselves. A topic that is
65
+literally built on top of `next` cannot be merged to `master` without
66
+dragging in all the other topics in `next`, some of which may not be
67
+ready.
68
69
For example, if you are making tree-wide changes, while somebody else is
70
also making their own tree-wide changes, your work may have severe