From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: zfs: update to 0.8.3
Date: Thu, 13 Feb 2020 14:05:08 +0100 [thread overview]
Message-ID: <20200213130508.QpiiC7cbe6At0PmcFGPvgtQgYeE0SvQUTil3mVRCztU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19079@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/19079#issuecomment-585744851
Comment:
> Why not use vsed here?
Only because I tend to forget that `vsed` exists. Upstream is aware of the redirection issue the `sed` line is intended to fix and is reviewing a (one-line) patch to correct the problem. I think there is a high probability at the `sed` line (and the `bash` runtime dependency) will be removed in the next package update.
prev parent reply other threads:[~2020-02-13 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19079@inbox.vuxu.org>
2020-02-13 8:34 ` voidlinux-github
2020-02-13 13:05 ` voidlinux-github [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=20200213130508.QpiiC7cbe6At0PmcFGPvgtQgYeE0SvQUTil3mVRCztU@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).