diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2013-11-10 09:20:52 -0500 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2013-11-10 14:48:29 -0500 |
| commit | 001e114b8d59f4eaf2a314a2bc5e57078afdf82f (patch) | |
| tree | 606fa622be346ef917886a29aea7e17383e00d31 /src/tools/RELEASE_CHANGES | |
| parent | dca09ac53329e92d73f45674957c26d3d7ae5117 (diff) | |
| download | postgresql-001e114b8d59f4eaf2a314a2bc5e57078afdf82f.tar.gz | |
Fix whitespace issues found by git diff --check, add gitattributes
Set per file type attributes in .gitattributes to fine-tune whitespace
checks. With the associated cleanups, the tree is now clean for git
Diffstat (limited to 'src/tools/RELEASE_CHANGES')
| -rw-r--r-- | src/tools/RELEASE_CHANGES | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/tools/RELEASE_CHANGES b/src/tools/RELEASE_CHANGES index 91b3825176..321f37cd37 100644 --- a/src/tools/RELEASE_CHANGES +++ b/src/tools/RELEASE_CHANGES @@ -89,7 +89,7 @@ Starting a New Development Cycle Creating Back-Branch Release Notes ================================== -* Run src/tools/git_changelog to generate a list of relevant commits. +* Run src/tools/git_changelog to generate a list of relevant commits. You can also run 'git log' in each branch. Be sure to use the --since branch tag and not the release date, as commits could have been done between branch stamping and the release date. @@ -99,9 +99,9 @@ Creating Back-Branch Release Notes should include more small change details because testing is limited. * Copy this into older branches' release-N.N.sgml files, then remove - items that do not apply based on commit logs for that branch. + items that do not apply based on commit logs for that branch. -* Add any older branch commits not in the newest branch. This can be +* Add any older branch commits not in the newest branch. This can be accomplished by diff'ing the newest and older branch commit logs and looking for lines that only appear in the older branch, e.g.: |