This is what I used to do for the old releases (from 8.2
tools/README.txt, from show 6168f3ebf046e4c3d5561bfa96a39d0f02b771db):
index 42c71fd52d..64666eb550 100644
--- a/tools/README.txt
+++ b/tools/README.txt
@@ -745,15 +745,6 @@ link.sh, link.bat, copydir.sh, copydir.bat,
unlink.sh, and unlink.bat
NTFS mklink.exe command instead of copying files. That logic, however,
has not been verified as of this writing.
-logparser.c
------------
-
- Convert a git log to ChangeLog format. Recommended usage:
-
- git log --date-order --reverse <rev1>..<rev2>|HEAD >_git_log.tmp
- logparser _git_log.tmp >_changelog.txt
- rm -f _git_log.tmp
-
On 5/22/2020 2:54 PM, Brennan Ashton wrote:
On Fri, May 22, 2020, 1:49 PM Brennan Ashton <bash...@brennanashton.com>
wrote:
You want to find the point at which it was branched, something like
git log master..releasebranch --oneline | tail -1
Then you can use it for the base of log
git log branched-commit..master
Nevermind I see what you were asking for. There is no great way to do this
with git directly, usually you track this by using labels (or similar) on
issues or PRs to aggregate it. At least that is that is how I have always
run releases for work.
--Brennan
