public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Proposed patch for web site: update most links to HTTPS
Date: Mon, 23 May 2016 10:35:00 -0000	[thread overview]
Message-ID: <20160523103519.GA30229@calimero.vinschen.de> (raw)
In-Reply-To: <BL2PR03MB2289CA95EC0CCF0D42AB961DF4D0@BL2PR03MB228.namprd03.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]

On May 22 00:29, Brian Clifton wrote:
> >On Apr 24 17:18, Brian Clifton wrote:
> >> Hi folks,
> >> 
> >> I have a proposed change for the web site. This patch (see below) will update most of the urls to HTTPS. In many cases there was a redirect; for those I captured the new canonical address.
> >> 
> >> (Per the https://cygwin.com/contrib.html, this is *not* a change to 
> >> anything in the winsup directory, which is why I chose the 
> >> cygwin@cygwin distro)
> >> 
> >> The patch can be found here:
> >> https://patch.clifton.io/cygwin/cygwin-htdocs_bsclifton_https_20160424
> >> .patch
> >
> >Thanks for the patch, but, here's a question:
> >
> >Since Cygwin.com redirects http requests to https anyway, all links to cygwin.com (or, FWIW, sourceware.org) will end up as https requests anyway.
> >
> >Having said that, wouldn't it make sense then to avoid absolute links to cygwin.com and rather convert them to relative links, i.e.:
> >
>   >-<a href="http://cygwin.com/ml/cygwin/2003-03/msg02182.html">Inspired</a> by
>   >+<a href="/ml/cygwin/2003-03/msg02182.html">Inspired</a> by
> >
> >?
> >
> >
> >Thanks,
> >Corinna
> 
> Good points Corinna; I updated the patch to use relative URLs (attached). If the attachment does not work for some reason, it can also be downloaded from here:
> https://patch.clifton.io/cygwin/cygwin-htdocs_bsclifton_https_20160521.patch

Thanks for doing that, but this patch can't apply.  Please note that the
cygwin-api, cygwin-ug-net, and faq subdirs are maintained as part of the
cygwin repo itself and are in XML, not in HTML.  Only the generic stuff
is maintained in the htdocs repo.

On second thought, using relative paths inside the Cygwin docs
(cygwin-api, cygwin-ug-net, and faq) is not such a bright idea, because
the docs should ideally work even if not on the cygwin.com website.
Sorry about that, but I didn't notice that your patch also changes
the Cygwin docs :}

Can you please split up the patch in two chunks?

The generic website patches should be based on the Website git repo at

  git://sourceware.org/git/cygwin-htdocs.git

the Cygwin docs patches on the Cygwin git repo at

  git://sourceware.org/git/newlib-cygwin.git.

The docs XML files are in the winsup/doc subdir.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-05-23 10:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25  0:05 Brian Clifton
2016-04-25  0:29 ` Andrey Repin
2016-04-25  5:50   ` Brian Clifton
2016-04-25  6:10     ` Andrey Repin
2016-04-25 13:20       ` Adam Dinwoodie
2016-04-25 17:41         ` Andrey Repin
2016-04-26 10:17           ` Csaba Raduly
2016-04-25 19:59         ` Nellis, Kenneth
2016-04-25 20:46           ` Vince Rice
2016-04-25 23:18             ` Brian Clifton
2016-04-26 19:19               ` Achim Gratz
2016-04-27 10:18         ` Linda Walsh
2016-05-20 16:36 ` Corinna Vinschen
2016-05-20 20:47   ` Warren Young
2016-05-22  0:30   ` Brian Clifton
2016-05-23 10:35     ` Corinna Vinschen [this message]
2016-05-24 12:42       ` Warren Young
2016-05-24 16:59         ` Corinna Vinschen
2016-05-24 18:55           ` Warren Young
2016-06-12 10:13       ` Brian Clifton
2016-06-14 19:20         ` Corinna Vinschen

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=20160523103519.GA30229@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).