From: amak79 <amak79@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Manual.md: fix package naming conventions anchor
Date: Fri, 30 Oct 2020 04:51:54 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25977@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 330 bytes --]
There is a new pull request by amak79 against master on the void-packages repository
https://github.com/amak79/void-packages manual
https://github.com/void-linux/void-packages/pull/25977
Manual.md: fix package naming conventions anchor
A patch file from https://github.com/void-linux/void-packages/pull/25977.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-manual-25977.patch --]
[-- Type: text/x-diff, Size: 802 bytes --]
From 5acb7845656e7ba98737b25af785e05f111314c8 Mon Sep 17 00:00:00 2001
From: amak <amak.git@outlook.com>
Date: Fri, 30 Oct 2020 14:46:30 +1100
Subject: [PATCH] Manual.md: fix package naming conventions anchor
---
Manual.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Manual.md b/Manual.md
index 4af3a7b78d9..5b1266ba715 100644
--- a/Manual.md
+++ b/Manual.md
@@ -8,7 +8,7 @@ packages for XBPS, the `Void Linux` native packaging system.
* [Introduction](#Introduction)
* [Quality Requirements](#quality_requirements)
* [Package build phases](#buildphase)
- * [Package naming conventions](#namingconvention)
+ * [Package naming conventions](#namingconventions)
* [Libraries](#libs)
* [Language Modules](#language_modules)
* [Language Bindings](#language_bindings)
next reply other threads:[~2020-10-30 3:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 3:51 amak79 [this message]
2020-10-30 19:05 ` [PR PATCH] [Merged]: " abenson
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25977@inbox.vuxu.org \
--to=amak79@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).