Github messages for voidlinux
 help / color / mirror / Atom feed
From: meator <meator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Document changelog variable in Manual.md
Date: Fri, 20 Aug 2021 08:47:10 +0200	[thread overview]
Message-ID: <20210820064710.LmoDBU9zeFofKOlOK7_ERncyRja4yUZu0EZzX151bmw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32586@inbox.vuxu.org>

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

There is an updated pull request by meator against master on the void-packages repository

https://github.com/meator/void-packages patch-1
https://github.com/void-linux/void-packages/pull/32586

Document changelog variable in Manual.md
[ci skip]

A patch file from https://github.com/void-linux/void-packages/pull/32586.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-1-32586.patch --]
[-- Type: text/x-diff, Size: 1127 bytes --]

From 726239197ac1770167e6527e75f50a4349c74d4a Mon Sep 17 00:00:00 2001
From: meator <Coder64@protonmail.com>
Date: Thu, 19 Aug 2021 15:37:31 +0200
Subject: [PATCH] Manual.md: document changelog and modify homepage

---
 Manual.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/Manual.md b/Manual.md
index 4316363f66c4..33706f20c210 100644
--- a/Manual.md
+++ b/Manual.md
@@ -434,7 +434,7 @@ in this directory such as `${XBPS_BUILDDIR}/${wrksrc}`.
 
 The list of mandatory variables for a template:
 
-- `homepage` A string pointing to the `upstream` homepage.
+- `homepage` An URL pointing to the upstream homepage.
 
 
 - <a id="var_license"></a>
@@ -743,6 +743,8 @@ used.
 
 - `fetch_cmd` Executable to be used to fetch URLs in `distfiles` during the `do_fetch` phase.
 
+- `changelog` An URL pointing to the upstream changelog. Raw text files are preferred.
+
 - `archs` Whitespace separated list of architectures that a package can be
 built for, available architectures can be found under `common/cross-profiles`.
 In general, `archs` should only be set if the upstream software explicitly targets

  parent reply	other threads:[~2021-08-20  6:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19 13:52 [PR PATCH] " meator
2021-08-19 18:25 ` [PR REVIEW] " ericonr
2021-08-19 21:25 ` paper42
2021-08-20  6:46 ` meator
2021-08-20  6:47 ` meator [this message]
2021-08-23 19:10 ` [PR PATCH] [Merged]: " Chocimier

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=20210820064710.LmoDBU9zeFofKOlOK7_ERncyRja4yUZu0EZzX151bmw@z \
    --to=meator@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).