Created attachment 245873 [details] Upgrade patch This patch upgrades the Limine bootloader to the latest version: 5.20231024.0.
Is there a changelog for this update? Please place a link to the changelog in the URL field or list the changes in a comment.
Created attachment 245964 [details] Update patch Limine 5.20231029.0 was released upstream and it contains a ChangeLog file. I hope updating the bug to 5.20231029.0 from 5.20231024.0 suffices.
Created attachment 246075 [details] Update patch
(In reply to mintsuki from comment #3) What changed between this patch and the previous one?
(In reply to Robert Clausecker from comment #4) I updated the patch to the latest upstream version: 5.20231103.0 from 5.20231029.0.
Can you please link the changelog so I can include it in the commit message? You should do so whenever you submit a patch to update a port.
(In reply to Robert Clausecker from comment #6) The changelog file is inside the tarball and generated upstream... what link should I provide?
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=e28ca0b21024e32c697d2ba6aff1d1eeb187f498 commit e28ca0b21024e32c697d2ba6aff1d1eeb187f498 Author: mintsuki <mintsuki@protonmail.com> AuthorDate: 2023-11-03 07:20:20 +0000 Commit: Robert Clausecker <fuz@FreeBSD.org> CommitDate: 2023-11-03 21:16:25 +0000 sysutils/limine: Update to 5.20231103.0 PR: 274725 sysutils/limine/Makefile | 4 ++-- sysutils/limine/distinfo | 6 +++--- sysutils/limine/pkg-plist | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-)
A link to the changelog of some sort. If you can't do that, include the changelog in the commit message of your patch file or add it as a commit. A list of commits is usually a poor changelog, but if you don't have anything better... Anyway, I've now pushed the patch without the changelog as some patches in my current batch need to be committed urgently.