From: Eric Sunshine <sunshine@sunshineco.com>
To: Josh Soref <jsoref@gmail.com>
Cc: Josh Soref via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH 2/4] doc: update links to current pages
Date: Fri, 22 Sep 2023 17:34:14 -0400 [thread overview]
Message-ID: <CAPig+cT7G2G-PQ05cSAxLLoZPbz4eyHjPxUjMWhDB5ondyD0sA@mail.gmail.com> (raw)
In-Reply-To: <CACZqfqC_UwSPfn0f9L4TfkYDGU64t_en6=7wYMsnxA9fB2rSjw@mail.gmail.com>
On Fri, Sep 22, 2023 at 5:31 PM Josh Soref <jsoref@gmail.com> wrote:
> Eric Sunshine wrote:
> > > - * [2] http://json.org/
> > > + * [2] https://www.json.org/
> >
> > Not sure why this change is needed considering that the simpler
> > s/http/https/ seems sufficient.
>
> This is because that's their preference:
>
> ```sh
> % curl -s http://json.org/|grep REFRESH
> <meta HTTP-EQUIV="REFRESH" content="0;
> url=https://www.JSON.org/json-en.html"></head>
> ```
>
> It's somewhat traditional to respect sites' self-identification.
It might be worth calling that out in the commit message of both
patches if you happen to reroll so other reviewers understand the
motivation. (That said, on its own, it's probably not worth a reroll.)
next prev parent reply other threads:[~2023-09-22 21: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 [this message]
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 ` [PATCH v2 0/4] Switch links to https Junio C Hamano
2023-09-25 18:55 ` 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=CAPig+cT7G2G-PQ05cSAxLLoZPbz4eyHjPxUjMWhDB5ondyD0sA@mail.gmail.com \
--to=sunshine@sunshineco.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).