From: MeganerdNL <MeganerdNL@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Update fail2ban to newest stable
Date: Sun, 02 Jul 2023 15:12:10 +0200 [thread overview]
Message-ID: <20230702131210.twqxcqyENCGJxohtWzsMEG1CGDQYl76TxlaV6T7Fot0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44787@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 424 bytes --]
New comment by MeganerdNL on void-packages repository
https://github.com/void-linux/void-packages/pull/44787#issuecomment-1616657276
Comment:
> @MeganerdNL You may want to read https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#committing-your-changes on how to format commits.
Thanks. Sorry, I did read it, but thought using git only was ok too.
If it's a requirement I will use it from now on.
next prev parent reply other threads:[~2023-07-02 13:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 12:18 [PR PATCH] " MeganerdNL
2023-07-02 12:50 ` necrophcodr
2023-07-02 12:56 ` [PR REVIEW] " necrophcodr
2023-07-02 13:04 ` mhmdanas
2023-07-02 13:10 ` MeganerdNL
2023-07-02 13:12 ` MeganerdNL [this message]
2023-07-02 13:12 ` MeganerdNL
2023-07-02 13:39 ` Bnyro
2023-07-02 18:15 ` [PR PATCH] [Updated] " MeganerdNL
2023-07-02 18:19 ` MeganerdNL
2023-07-02 18:28 ` [PR PATCH] [Updated] " MeganerdNL
2023-07-02 18:28 ` MeganerdNL
2023-07-02 20:00 ` [PR PATCH] [Updated] fail2ban: update to 1.0.2 MeganerdNL
2023-07-02 20:12 ` Bnyro
2023-07-02 20:39 ` MeganerdNL
2023-07-02 20:43 ` Bnyro
2023-07-02 20:43 ` Bnyro
2023-07-02 20:48 ` [PR PATCH] [Updated] " MeganerdNL
2023-07-02 20:51 ` MeganerdNL
2023-07-02 20:55 ` Bnyro
2023-07-03 17:19 ` [PR PATCH] [Updated] " MeganerdNL
2023-07-03 17:50 ` MeganerdNL
2023-07-04 22:34 ` [PR PATCH] [Merged]: " Duncaen
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=20230702131210.twqxcqyENCGJxohtWzsMEG1CGDQYl76TxlaV6T7Fot0@z \
--to=meganerdnl@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).