From: Paul Menzel <paulepanter@users.sourceforge.net>
To: dri-devel@lists.freedesktop.org
Subject: Please use HTTPS URLs for Patchwork references
Date: Sun, 16 Jul 2017 11:26:38 +0200 [thread overview]
Message-ID: <1500197198.4493.56.camel@users.sourceforge.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 622 bytes --]
Dear Linux folks,
Currently commits contain non HTTPS URLs like below.
```
Link: http://patchwork.freedesktop.org/patch/msgid/20170601143619.27840-7-ville.syrjala@linux.intel.com
```
I guess these are generated by scripts. Could you please update them to
generate HTTPS URLs, as that’s where the “non-secure” URLs are
redirected to?
```
$ curl -I http://patchwork.freedesktop.org
HTTP/1.1 301 Moved Permanently
Date: Sun, 16 Jul 2017 09:25:15 GMT
Server: Apache/2.4.10 (Debian)
Location: https://patchwork.freedesktop.org/
Content-Type: text/html; charset=iso-8859-1
```
Thanks,
Paul
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2017-07-16 9:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1500197198.4493.56.camel@users.sourceforge.net \
--to=paulepanter@users.sourceforge.net \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.