From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: fail2ban: update to 0.11.2_3.
Date: Wed, 19 Jan 2022 18:29:28 +0100 [thread overview]
Message-ID: <20220119172928.97BScGlcxXLsk_J0pBsZwgz-DXfhbSpRnsIYcCamPww@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35123@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 364 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/pull/35123#issuecomment-1016698773
Comment:
Its not enough, thats useless information, it tells us nothing, revision increases usually have a reason, be it rebuilds for updated dependencies or patches, but its important to document that reason in the commit message.
next prev parent reply other threads:[~2022-01-19 17:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 14:27 [PR PATCH] " ftpd
2022-01-19 17:10 ` Duncaen
2022-01-19 17:20 ` ftpd
2022-01-19 17:29 ` Duncaen [this message]
2022-01-19 17:49 ` ftpd
2022-01-19 17:51 ` fail2ban: update revision to 0.11.2_3 to make it work with python 3.10 ftpd
2022-01-20 9:46 ` [PR PATCH] [Updated] " ftpd
2022-01-20 9:50 ` [PR PATCH] [Updated] fail2ban: add patch for " ftpd
2022-01-20 9:53 ` ftpd
2022-01-20 10:01 ` [PR PATCH] [Merged]: " paper42
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=20220119172928.97BScGlcxXLsk_J0pBsZwgz-DXfhbSpRnsIYcCamPww@z \
--to=duncaen@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).