mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix incorrect use of term HEAD for Git

Browse Source 
HEAD as used here was CVS terminology.  Now we mean master.
This commit is contained in:
Peter Eisentraut 2019-10-07 09:44:17 +02:00
parent caa078353e
commit cc4ec2d29a
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/tools/RELEASE_CHANGES
View File

@ -31,9 +31,9 @@ For Major Releases
(in addition to the above)
Note that once the release branch has been forked off in git,
release-note editing happens in that branch, not in HEAD.
release-note editing happens in that branch, not in master.
Updates to the rest of the documentation usually need to happen
in both HEAD and the branch.
in both master and the branch.
* Release notes
o use src/tools/git_changelog
@ -120,7 +120,7 @@ Creating Back-Branch Release Notes
diff commit-N.N.log commit-O.O.log | grep '^>'
* On the most recent release branch (*not* in HEAD), edit and create SGML
* On the most recent release branch (*not* in master), edit and create SGML
markup for relevant changes in that branch's release-NN.sgml file.
Minor release notes should include more small change details because
testing is limited.

2
src/tools/git_changelog
View File

@ -39,7 +39,7 @@
# shows the last commit before that branch was made.
#
# Note that --master-only is an imperfect filter, since it will not detect
# cases where a HEAD patch was back-patched awhile later or with a slightly
# cases where a master patch was back-patched awhile later or with a slightly
# different commit message. To find such cases, it's a good idea to look
# through the output of
# git_changelog --non-master-only --oldest-first --since='start-date'