From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: rc: fix dead links
Date: Sun, 12 Sep 2021 19:12:52 +0200 [thread overview]
Message-ID: <20210912171252.5-PRrgjBjuMamBFtFlJ-P2g6G6IWOGDqfvz-CfwY8NE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32875@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
There's a merged pull request on the void-packages repository
rc: fix dead links
https://github.com/void-linux/void-packages/pull/32875
Description:
<!-- Mark items with [x] where applicable -->
`rc` seems pretty dead now. `tobold.org` and `static.tobold.org` are down. I have tried to contact the author, but his email seems to be down too. This package should maybe be removed rather than fixed.
This PR fixes dead links and modifies the build process.
@leahneukirchen I'm pinging you since you are the maintainer of `rc`. Do you have any comment on this?
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR
prev parent reply other threads:[~2021-09-12 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 8:21 [PR PATCH] " meator
2021-09-08 9:40 ` [PR PATCH] [Updated] " meator
2021-09-08 9:53 ` leahneukirchen
2021-09-12 16:27 ` leahneukirchen
2021-09-12 16:42 ` [PR PATCH] [Updated] " meator
2021-09-12 16:42 ` meator
2021-09-12 16:48 ` ericonr
2021-09-12 17:05 ` [PR PATCH] [Updated] " meator
2021-09-12 17:12 ` leahneukirchen [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=20210912171252.5-PRrgjBjuMamBFtFlJ-P2g6G6IWOGDqfvz-CfwY8NE@z \
--to=leahneukirchen@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).