On 3/4/24 07:24, Kevin Bloom wrote:
Jason Bacon <jtocino%gmx.com@localhost> wrote:FYI, however verbose you want to be in the commit log (this is a matter of personal taste), I would always add a link to upstream's changelog if there is one. In this case: https://github.com/claudiodangelis/qrcp/releasesGood idea -- It shall be done. Do you usually place it at the top or the bottom of the message? Also, thank you for comitting :)
I usually put "highlights" of the change log (summary of what seem like the most important changes + general description of the rest) in the commit message, and the link to the upstream change log below that for anyone who might want more details. E.g. devel/libxtend: Update to 0.1.9 xt_fopen(): Call stat() before popen() and return NULL if file does not exist xt_fopen(): Add lz4 support Add XT_COMPRESSION_EXTENSIONS, a list of possible filename extensions Clean up some compiler warnings Changes: https://github.com/outpaddling/libxtend/releases