diff options
| author | Junio C Hamano <gitster@pobox.com> | 2023-07-25 22:17:31 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2023-07-27 13:06:20 -0700 |
| commit | f835de52d7c36c278004383919c58457861dac6c (patch) | |
| tree | e76e902b07da9ce22263c5b69c9df9352fda9fa7 /commit.c | |
| parent | 37f6040764489ee63b14807c1196c3b2e6469eb4 (diff) | |
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>
Diffstat (limited to 'commit.c')
0 files changed, 0 insertions, 0 deletions