From: bsdelf <bsdelf@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: netatalk-3.1.15
Date: Sat, 15 Jul 2023 11:03:37 +0200 [thread overview]
Message-ID: <20230715090337.EO18yA24X5zORh_wYQtHX1aWLUL8wnVl-Nh3y4v16OY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45011@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 565 bytes --]
New comment by bsdelf on void-packages repository
https://github.com/void-linux/void-packages/pull/45011#issuecomment-1636715255
Comment:
Should I fix the lint? Why is space not preferred by the way?
```
Error: please indent with tabs
```
> ```diff
> -conf_files="
> - /etc/dbus-1/system.d/netatalk-dbus.conf
> - /etc/extmap.conf
> - /etc/afp.conf
> - /etc/dbus-session.conf"
>
> +conf_files="
> + /etc/dbus-1/system.d/netatalk-dbus.conf
> + /etc/extmap.conf
> + /etc/afp.conf
> + /etc/dbus-session.conf"
> ```
next prev parent reply other threads:[~2023-07-15 9:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 8:54 [PR PATCH] " bsdelf
2023-07-13 13:59 ` [PR REVIEW] " Duncaen
2023-07-14 6:22 ` bsdelf
2023-07-14 6:47 ` bsdelf
2023-07-14 17:46 ` Duncaen
2023-07-14 17:59 ` [PR REVIEW] " Chocimier
2023-07-15 3:30 ` bsdelf
2023-07-15 5:34 ` [PR PATCH] [Updated] " bsdelf
2023-07-15 5:58 ` bsdelf
2023-07-15 6:27 ` bsdelf
2023-07-15 8:53 ` [PR REVIEW] " Chocimier
2023-07-15 9:03 ` bsdelf [this message]
2023-07-15 9:09 ` Chocimier
2023-07-15 9:17 ` [PR PATCH] [Updated] " bsdelf
2023-07-15 9:24 ` bsdelf
2023-07-23 8:56 ` [PR PATCH] [Updated] " bsdelf
2023-07-23 9:05 ` bsdelf
2023-07-23 9:30 ` bsdelf
2023-08-09 10:05 ` [PR PATCH] [Updated] " bsdelf
2023-08-09 10:18 ` bsdelf
2023-11-08 1:45 ` github-actions
2023-11-18 6:36 ` [PR PATCH] [Updated] " bsdelf
2024-02-18 1:46 ` github-actions
2024-03-04 1:47 ` [PR PATCH] [Closed]: " github-actions
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=20230715090337.EO18yA24X5zORh_wYQtHX1aWLUL8wnVl-Nh3y4v16OY@z \
--to=bsdelf@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).