| commit | 369998df83d779e0b3fc45072be20d43a6559b27 | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Wed, 26 Jul 2023 05:21:12 +0000 (25 22:21 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 27 Jul 2023 20:07:40 +0000 (27 13:07 -0700) | ||
| tree | a3a32a8c170752578c86adde7abd068721ffc6d2 | treesnapshot (tar.gz zip) |
| parent | f835de52d7c36c278004383919c58457861dac6c | commitdiff |
SubmittingPatches: use of older maintenance tracks is an exception
While we could technically fix each and every bug on top of the
commit that introduced it, it is not necessarily practical. For
trivial and low-value bugfixes, it often is simpler and sufficient
to just fix it in the current maintenance track, leaving the bug
unfixed in the older maintenance tracks.
Demote the "use older maintenance track to fix old bugs" as a side
note, and explain that the choice is used only in exceptional cases.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
While we could technically fix each and every bug on top of the
commit that introduced it, it is not necessarily practical. For
trivial and low-value bugfixes, it often is simpler and sufficient
to just fix it in the current maintenance track, leaving the bug
unfixed in the older maintenance tracks.
Demote the "use older maintenance track to fix old bugs" as a side
note, and explain that the choice is used only in exceptional cases.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/SubmittingPatches | diffblobblamehistory |