Date: Wed, 22 Nov 2023 08:37:38 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 275240] sysutils/limine: Update to 5.20231121.0 Message-ID: <bug-275240-7788-Kpfcot1vAI@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275240-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-275240-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275240 Robert Clausecker <fuz@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fuz@FreeBSD.org Status|New |In Progress --- Comment #1 from Robert Clausecker <fuz@FreeBSD.org> --- That changelog is just a list of git commits without time stamps or any information as to what versions the commits correspond to. It's pretty much useless any I will not include it in the commit message. It's literally wo= rse than just linking the auto-generated =20=20=20 https://github.com/limine-bootloader/limine/compare/v5.20231114.1...v5.2023= 1121.0 It would be better if there was an actual changelog, summarising the changes that took place so it's easy to see if there's anything to pay attention to= .=20 Yes, this is something I'm asking you (or more specifically, the upstream) = to write. It cannot be auto-generated. If you attempt to generate a changelog automatically anyway (which I strong= ly recommend against as that's not particularly helpful), at least take the courtesy and produce it in such a way that it's easy to see which version corresponds to which commit. E.g. you can do "git log --oneline <previous tag>..<this tag>" to generate a log of changes since the previous tag and includes any tags that exist so it's easy to see which commits correspond to what. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-275240-7788-Kpfcot1vAI>