From: NeelChotai <NeelChotai@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Manual.md: indicate 80 character line limit
Date: Fri, 26 Mar 2021 21:11:01 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29765@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
There is a new pull request by NeelChotai against master on the void-packages repository
https://github.com/NeelChotai/void-packages template-line-limit
https://github.com/void-linux/void-packages/pull/29765
Manual.md: indicate 80 character line limit
@ericonr do you think this is enough of an indication or would an example be helpful?
A patch file from https://github.com/void-linux/void-packages/pull/29765.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-template-line-limit-29765.patch --]
[-- Type: text/x-diff, Size: 744 bytes --]
From 613d7cca1b3c12a632cdade8dcf0f77f416e413f Mon Sep 17 00:00:00 2001
From: Neel Chotai <neel@chot.ai>
Date: Fri, 26 Mar 2021 20:05:46 +0000
Subject: [PATCH] Manual.md: indicate 80 character line limit
---
Manual.md | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Manual.md b/Manual.md
index 4439865e1d73..e2979fbec51b 100644
--- a/Manual.md
+++ b/Manual.md
@@ -88,6 +88,9 @@ By convention, all templates start with a comment briefly explaining what they
are. In addition, pkgname and version can't have any characters in them that
would require them to be quoted, so they are not quoted.
+Try to break any lines over 80 characters where it makes sense, e.g. in
+dependencies.
+
A simple `template` example is as follows:
```
next reply other threads:[~2021-03-26 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 20:11 NeelChotai [this message]
2021-03-26 20:20 ` ericonr
2021-03-26 21:40 ` [PR PATCH] [Closed]: " NeelChotai
2021-03-26 21:58 ` ericonr
2021-03-26 22:04 ` NeelChotai
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-29765@inbox.vuxu.org \
--to=neelchotai@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).