git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Josh Soref via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Josh Soref <jsoref@gmail.com>
Subject: Re: [PATCH v2 0/4] Switch links to https
Date: Mon, 25 Sep 2023 11:33:59 -0700	[thread overview]
Message-ID: <xmqq34z2ump4.fsf@gitster.g> (raw)
In-Reply-To: <pull.1589.v2.git.1695553041.gitgitgadget@gmail.com> (Josh Soref via GitGitGadget's message of "Sun, 24 Sep 2023 10:57:17 +0000")

"Josh Soref via GitGitGadget" <gitgitgadget@gmail.com> writes:

> There are a couple of categories of http links

The same comment applies to the previous round, but it is not clear
how the categories of links that are HTTP in the current code (the
first enumeration) are related to how HTTP links are modified in the
series (the second enumeration).  It is not like how the first one
in the first list (i.e. must be HTTP) is handled is described by the
first one in the second list (i.e. replace HTTP to HTTPS without
doing anything else), as the number of bullet points are different.

>  * links that are required to be http: because they're copied from something
>    that mandates it (the apache license, xml namespaces, xsl docbook
>    things?)

So these are in "must stay as-is" category?

>  * pages which exist at both http: and https: and can be safely switched

"Can be switched" does not mean we should switch, does it?

>  * pages that have jittered a bit but are now available as https:

... but not available over HTTP:?  If so, this falls into "must
switch to avoid a dangling link" category?

>  * pages that have jittered a bit and are not available over https:

Again, "must stay as-is"?

>  * pages that are gone and for which the best source is
>    https://web.archive.org

Unfortunate, but definitely improves things.

>  * urls that were imaginary

What is done to them?  Just leave them as they are, or replace with
another imaginary link over HTTPS?

Hopefully we will see in the proposed commit log message of
individual patches what kind of http:// links the patch deals with
and how (e.g. "For some URLs in the documentation and the code, the
original http:// links are not reachable and dangling but the same
contents are still available at https://; for these URLs, replace
http:// with https:// without doing anything else.").  Let's read
on.

> In order:
>
>  * doc: switch links to https -- the simplest
>  * doc: update links to current pages -- I found the current pages for
>    these, it should be easy enough to verify these / reject them
>  * doc: update links for andre-simon.de -- I've split this out, I don't like
>    the idea of having to download binaries over http. If this were my
>    project, I'd be tempted to remove the feature or self-host w/ https...
>  * doc: refer to internet archive -- the original urls are dead, I've found
>    internet archive date links for them. (There are some in git already, so
>    this seemed like a very reasonable choice.)



> cc: Eric Sunshine sunshine@sunshineco.com cc: Josh Soref jsoref@gmail.com

(administrivia) I am not sure what effect, if any, this line has.

  parent reply	other threads:[~2023-09-25 18:34 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22 14:13 [PATCH 0/4] Switch links to https Josh Soref via GitGitGadget
2023-09-22 14:13 ` [PATCH 1/4] doc: switch " Josh Soref via GitGitGadget
2023-09-22 21:22   ` Eric Sunshine
2023-09-22 22:05   ` Junio C Hamano
2023-09-22 14:13 ` [PATCH 2/4] doc: update links to current pages Josh Soref via GitGitGadget
2023-09-22 21:25   ` Eric Sunshine
2023-09-22 21:30     ` Josh Soref
2023-09-22 21:34       ` Eric Sunshine
2023-09-22 22:21   ` Junio C Hamano
2023-09-22 22:23   ` Junio C Hamano
2023-09-22 14:13 ` [PATCH 3/4] doc: update links for andre-simon.de Josh Soref via GitGitGadget
2023-09-22 14:13 ` [PATCH 4/4] doc: refer to internet archive Josh Soref via GitGitGadget
2023-09-24 10:57 ` [PATCH v2 0/4] Switch links to https Josh Soref via GitGitGadget
2023-09-24 10:57   ` [PATCH v2 1/4] doc: switch " Josh Soref via GitGitGadget
2023-11-23 21:19     ` Elijah Newren
2023-11-24  3:12       ` Josh Soref
2023-11-24 15:33         ` Elijah Newren
2023-09-24 10:57   ` [PATCH v2 2/4] doc: update links to current pages Josh Soref via GitGitGadget
2023-11-23 21:27     ` Elijah Newren
2023-11-24  3:20       ` Josh Soref
2023-09-24 10:57   ` [PATCH v2 3/4] doc: update links for andre-simon.de Josh Soref via GitGitGadget
2023-09-24 10:57   ` [PATCH v2 4/4] doc: refer to internet archive Josh Soref via GitGitGadget
2023-11-23 21:33     ` Elijah Newren
2023-11-24  3:24       ` Josh Soref
2023-11-24 15:32         ` Elijah Newren
2023-09-25 18:33   ` Junio C Hamano [this message]
2023-09-25 18:55     ` [PATCH v2 0/4] Switch links to https Eric Sunshine
2023-11-24  3:35   ` [PATCH v3 " Josh Soref via GitGitGadget
2023-11-24  3:35     ` [PATCH v3 1/4] doc: update links to current pages Josh Soref via GitGitGadget
2023-11-24  3:35     ` [PATCH v3 2/4] doc: switch links to https Josh Soref via GitGitGadget
2023-11-24  3:35     ` [PATCH v3 3/4] doc: update links for andre-simon.de Josh Soref via GitGitGadget
2023-11-24  3:35     ` [PATCH v3 4/4] doc: refer to internet archive Josh Soref via GitGitGadget
2023-11-24 15:36     ` [PATCH v3 0/4] Switch links to https Elijah Newren
2023-11-24 16:03       ` Josh Soref
2023-11-27  0:49         ` Junio C Hamano

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=xmqq34z2ump4.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=jsoref@gmail.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 NNTP newsgroup(s).