From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: i3status-rust: update to 0.20.2.
Date: Wed, 21 Jul 2021 23:05:19 +0200 [thread overview]
Message-ID: <20210721210519.sQCUKrS1cjJmE7Gcp5bY22k58RAx6hNmSYH0FLDB_xw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32051@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 528 bytes --]
New comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/pull/32051#issuecomment-884499041
Comment:
@FIGBERT don't worry, my message was more directed at @ericonr due to the merge and less at you for the PR. Not everyone can know the intrinsics of contributing to everything, and the manual for this repo is so extremely long that it's not 100% reasonable to expect everycontributor to do thia, but we should handle it like this at least among those with write accessto the main repo
prev parent reply other threads:[~2021-07-21 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 4:50 [PR PATCH] " FIGBERT
2021-07-20 14:48 ` [PR PATCH] [Merged]: " ericonr
2021-07-21 6:41 ` jcgruenhage
2021-07-21 18:46 ` FIGBERT
2021-07-21 21:05 ` jcgruenhage [this message]
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=20210721210519.sQCUKrS1cjJmE7Gcp5bY22k58RAx6hNmSYH0FLDB_xw@z \
--to=jcgruenhage@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).