From: devvesa <devvesa@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sfeed_curses: update to 0.9.3
Date: Fri, 09 Oct 2020 09:29:30 +0200 [thread overview]
Message-ID: <20201009072930.mYoP1HztFh5oPnq3i1mnYxS7NNu0fuvHct7c6x_A2OU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25443@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 351 bytes --]
New comment by devvesa on void-packages repository
https://github.com/void-linux/void-packages/pull/25443#issuecomment-706020644
Comment:
Sorry, @sgn : I pushed it with too much confidence and then my child didn't allow me to spend more time to fix it. I promise to be more careful in the future and do less noise :pray: .
(I've opened a new PR)
next prev parent reply other threads:[~2020-10-09 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 13:14 [PR PATCH] " devvesa
2020-10-08 14:30 ` sgn
2020-10-08 14:30 ` [PR PATCH] [Closed]: " sgn
2020-10-09 7:29 ` devvesa [this message]
2020-10-09 11:47 ` sgn
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=20201009072930.mYoP1HztFh5oPnq3i1mnYxS7NNu0fuvHct7c6x_A2OU@z \
--to=devvesa@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).