| commit | c93dda2e785791c91fc2a9729b0bf03300fe43b3 | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Fri, 19 Jul 2024 20:44:35 +0000 (19 13:44 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 19 Jul 2024 20:53:53 +0000 (19 13:53 -0700) | ||
| tree | 7e29bfb585917aa404e55a8ff39d45dce736041e | treesnapshot (tar.gz zip) |
| parent | 337b4d400023d22207bcc3c29e9ebab31bf96fc2 | commitdiff |
howto-maintain: cover a whole development cycle
The "policy" part is more important than the "daily operation" part
in that it establishes why certain maintainer tasks exist and are
performed the way they are.
The text briefly touches the role each integration branches play in
the workflow, but does not give the whole picture of what happens in
a single development cycle using these branches. Extend the
description to describe a whole development cycle.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The "policy" part is more important than the "daily operation" part
in that it establishes why certain maintainer tasks exist and are
performed the way they are.
The text briefly touches the role each integration branches play in
the workflow, but does not give the whole picture of what happens in
a single development cycle using these branches. Extend the
description to describe a whole development cycle.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/howto/maintain-git.txt | diffblobblamehistory |