Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
cc4ec2d2
Commit
cc4ec2d2
authored
Oct 07, 2019
by
Peter Eisentraut
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix incorrect use of term HEAD for Git
HEAD as used here was CVS terminology. Now we mean master.
parent
caa07835
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
4 additions
and
4 deletions
+4
-4
src/tools/RELEASE_CHANGES
src/tools/RELEASE_CHANGES
+3
-3
src/tools/git_changelog
src/tools/git_changelog
+1
-1
No files found.
src/tools/RELEASE_CHANGES
View file @
cc4ec2d2
...
@@ -31,9 +31,9 @@ For Major Releases
...
@@ -31,9 +31,9 @@ For Major Releases
(in addition to the above)
(in addition to the above)
Note that once the release branch has been forked off in git,
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
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
* Release notes
o use src/tools/git_changelog
o use src/tools/git_changelog
...
@@ -120,7 +120,7 @@ Creating Back-Branch Release Notes
...
@@ -120,7 +120,7 @@ Creating Back-Branch Release Notes
diff commit-N.N.log commit-O.O.log | grep '^>'
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.
markup for relevant changes in that branch's release-NN.sgml file.
Minor release notes should include more small change details because
Minor release notes should include more small change details because
testing is limited.
testing is limited.
...
...
src/tools/git_changelog
View file @
cc4ec2d2
...
@@ -39,7 +39,7 @@
...
@@ -39,7 +39,7 @@
# shows the last commit before that branch was made.
# shows the last commit before that branch was made.
#
#
# Note that --master-only is an imperfect filter, since it will not detect
# 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
# different commit message. To find such cases, it's a good idea to look
# through the output of
# through the output of
# git_changelog --non-master-only --oldest-first --since='start-date'
# git_changelog --non-master-only --oldest-first --since='start-date'
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment