summaryrefslogtreecommitdiff
path: root/t/t7604-merge-custom-message.sh
diff options
context:
space:
mode:
authorLibravatar Raman Gupta <raman@rocketraman.com>2009-11-12 14:46:04 -0500
committerLibravatar Junio C Hamano <gitster@pobox.com>2009-11-20 23:39:58 -0800
commit382e54312220ac02586a3cbb06b0e4eb7789f043 (patch)
tree1736711f8d4558b0ce65826659dfd3255fc755f8 /t/t7604-merge-custom-message.sh
parentGIT 1.6.5 (diff)
downloadtgif-382e54312220ac02586a3cbb06b0e4eb7789f043.tar.xz
Add branch management for releases to gitworkflows
The current man page does a reasonable job at describing branch management during the development process, but it does not contain any guidance as to how the branches are affected by releases. Add a basic introduction to the branch management undertaken during a git.git release, so that a reader may gain some insight into how the integration, maintenance, and topic branches are affected during the release transition, and is thus able to better design the process for their own project. Other release activities such as reviews, testing, and creating distributions are currently out of scope. Signed-off-by: Nanako Shiraishi <nanako3@lavabit.com> Acked-by: Thomas Rast <trast@student.ethz.ch> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t7604-merge-custom-message.sh')
0 files changed, 0 insertions, 0 deletions