From: ng0 <ng0@n0.is>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 29830@debbugs.gnu.org
Subject: [bug#29830] suckless: Use https for suckless.org to address permanent redirects.
Date: Sat, 23 Dec 2017 22:36:28 +0000 [thread overview]
Message-ID: <20171223223628.555ylio5gs3m5ktk@abyayala> (raw)
In-Reply-To: <830a1246-00ee-917c-395a-febb4e3a718f@tobias.gr>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
Tobias Geerinckx-Rice transcribed 1.8K bytes:
> ng0,
>
> ng0 wrote on 23/12/17 at 23:03:
> > From efa667dfb5dcdc45eed10e4034ea88621404b69c Mon Sep 17 00:00:00 2001
> > From: ng0 <ng0@n0.is>
> > Date: Sat, 23 Dec 2017 21:53:40 +0000
> > Subject: [PATCH] gnu: suckless: Use https URLs.
> >
> > All suckless.org hosted URLs are now permanent redirects to https.
>
> Consider this pushed with a tweaked commit message once I finish testing
> some other queued patches.
>
> Are you working on this now, or are you merely trickling out finished
> patches? I ask because I had a very similar one ready to go, also
> changing all HTTP->HTTPS redirects to HTTPS :-/
>
> Kind regards,
>
> T G-R
>
I've pushed what I had, but there are many more left.
I don't plan to work on much more for the next weeks,
just maybe the people.mozilla.org issue. I've contacted
some upstream authors of software where the entire homepages
disappeared without a trace.
--
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
WWW: https://n0.is
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-23 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 22:03 [bug#29830] suckless: Use https for suckless.org to address permanent redirects ng0
2017-12-23 22:19 ` Tobias Geerinckx-Rice
2017-12-23 22:36 ` ng0 [this message]
2017-12-23 22:38 ` ng0
2017-12-23 23:02 ` bug#29830: " Tobias Geerinckx-Rice
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171223223628.555ylio5gs3m5ktk@abyayala \
--to=ng0@n0.is \
--cc=29830@debbugs.gnu.org \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).