From: Skaytacium <Skaytacium@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: update docker
Date: Mon, 03 May 2021 20:41:51 +0200 [thread overview]
Message-ID: <20210503184151.8xVls1exnCn4mUx7Fhzqdpqr3hSg-_J3I14KUiFnWO8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30244@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
New comment by Skaytacium on void-packages repository
https://github.com/void-linux/void-packages/pull/30244#issuecomment-831451926
Comment:
Any idea when this will actually get merged because all the tests seem to be passing and it's approved.
Currently, I had to compile `tini` manually and create a symlink to it in `/bin`, this could be automated pretty easily, and adds no breaking changes as far as I read into the PR and issue, to me it seems to be a problem of naming the package and including it?
It would be much better if the package was actually published and then all of this was discussed, as there are people like me who are trying to use docker-init, no offense meant at all, just my thoughts.
next prev parent reply other threads:[~2021-05-03 18:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 22:56 [PR PATCH] " radiden
2021-04-20 17:22 ` [PR PATCH] [Closed]: " radiden
2021-04-20 17:22 ` [PR PATCH] [Updated] " radiden
2021-04-20 17:39 ` radiden
2021-04-20 18:23 ` radiden
2021-04-20 18:52 ` pudiva
2021-04-20 19:09 ` pudiva
2021-04-20 19:10 ` pudiva
2021-04-20 19:43 ` ahesford
2021-04-20 21:39 ` endigma
2021-04-20 22:53 ` pudiva
2021-04-20 23:02 ` pudiva
2021-04-20 23:06 ` ahesford
2021-04-20 23:10 ` pudiva
2021-04-21 0:16 ` endigma
2021-04-21 0:17 ` endigma
2021-04-22 20:13 ` endigma
2021-05-03 18:38 ` Skaytacium
2021-05-03 18:41 ` Skaytacium [this message]
2021-05-03 18:45 ` [PR PATCH] [Merged]: " ahesford
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=20210503184151.8xVls1exnCn4mUx7Fhzqdpqr3hSg-_J3I14KUiFnWO8@z \
--to=skaytacium@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).