]> git.ipfire.org Git - thirdparty/git.git/commit
SubmittingPatches: explain why 'next' and above are inappropriate base
authorJunio C Hamano <gitster@pobox.com>
Wed, 26 Jul 2023 05:17:31 +0000 (22:17 -0700)
committerJunio C Hamano <gitster@pobox.com>
Thu, 27 Jul 2023 20:06:20 +0000 (13:06 -0700)
commitf835de52d7c36c278004383919c58457861dac6c
treee76e902b07da9ce22263c5b69c9df9352fda9fa7
parent37f6040764489ee63b14807c1196c3b2e6469eb4
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>
Documentation/SubmittingPatches