Github messages for voidlinux
 help / color / mirror / Atom feed
From: Jjp137 <Jjp137@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] wesnoth: update to 1.18.0.
Date: Thu, 28 Mar 2024 03:02:02 +0100	[thread overview]
Message-ID: <20240328020202.2F0A9213AC@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49545@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 572 bytes --]

New review comment by Jjp137 on void-packages repository

https://github.com/void-linux/void-packages/pull/49545#discussion_r1542223342

Comment:
```suggestion
changelog="https://github.com/wesnoth/wesnoth/blob/${version}/changelog.md"
```
Wesnoth has both stable and development releases, so it might be a good idea to link directly to the version-specific changelog. The release threads on the Wesnoth forums do this. Otherwise, as 1.19 development progresses, the changelog on the master branch will describe many changes that are not present in the stable version.

  parent reply	other threads:[~2024-03-28  2:02 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26  7:52 [PR PATCH] " iFoundSilentHouse
2024-03-26  9:12 ` iFoundSilentHouse
2024-03-26 10:16 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-03-26 10:30 ` iFoundSilentHouse
2024-03-26 10:40 ` iFoundSilentHouse
2024-03-26 10:46 ` iFoundSilentHouse
2024-03-26 10:58 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-03-26 11:03 ` iFoundSilentHouse
2024-03-26 11:07 ` iFoundSilentHouse
2024-03-26 11:07 ` iFoundSilentHouse
2024-03-26 11:12 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-03-26 11:13 ` iFoundSilentHouse
2024-03-26 13:21 ` iFoundSilentHouse
2024-03-26 18:23 ` iFoundSilentHouse
2024-03-26 18:25 ` iFoundSilentHouse
2024-03-26 20:09 ` [PR REVIEW] " classabbyamp
2024-03-26 20:23 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-03-26 22:56 ` iFoundSilentHouse
2024-03-27 10:05 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-03-27 10:08 ` iFoundSilentHouse
2024-03-27 10:08 ` iFoundSilentHouse
2024-03-27 10:15 ` iFoundSilentHouse
2024-03-27 10:25 ` iFoundSilentHouse
2024-03-27 11:17 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-03-27 11:48 ` iFoundSilentHouse
2024-03-28  1:51 ` Jjp137
2024-03-28  1:57 ` iFoundSilentHouse
2024-03-28  2:02 ` Jjp137 [this message]
2024-03-28  2:04 ` Jjp137
2024-03-28  2:09 ` iFoundSilentHouse
2024-03-28  2:09 ` iFoundSilentHouse
2024-03-28  2:17 ` [PR REVIEW] " classabbyamp
2024-03-28  2:23 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-03-28  2:38 ` iFoundSilentHouse
2024-03-28  2:41 ` [PR REVIEW] " classabbyamp
2024-03-28  2:44 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-03-28  2:51 ` iFoundSilentHouse
2024-03-28  2:52 ` [PR REVIEW] " iFoundSilentHouse
2024-03-28  5:29 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-03-28  5:33 ` iFoundSilentHouse
2024-03-31  4:54 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-05-18 16:36 ` [PR REVIEW] " classabbyamp
2024-05-27 19:23 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-05-27 19:25 ` [PR REVIEW] " iFoundSilentHouse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240328020202.2F0A9213AC@inbox.vuxu.org \
    --to=jjp137@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).