From: Jes Sorensen <jes.sorensen@gmail.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] Use more secure HTTPS URLs
Date: Thu, 14 May 2020 17:42:09 -0400 [thread overview]
Message-ID: <e83921a0-fed5-be7f-e5ff-5a3f37cb53ec@gmail.com> (raw)
In-Reply-To: <844fa4e8-fe19-ad46-55e3-1357518f1366@molgen.mpg.de>
On 5/14/20 4:39 PM, Paul Menzel wrote:
> Dear Jes,
>
>
> Am 13.05.20 um 15:44 schrieb Jes Sorensen:
>> On 5/13/20 9:27 AM, Paul Menzel wrote:
>>> All URLs in the source are available over HTTPS, so convert all URLs to
>>> HTTPS with the command below.
>>>
>>> git grep -l 'http://' | xargs sed -i 's,http://,https://,g'
>>>
>>> Cc: linux-raid@vger.kernel.org
>>> Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de>
>>
>> Some of this looks valid, but we're not going back to update existing
>> ANNOUNCE files.
>
> May I ask why? It’s all logged in the VCS history, and the two URLs are
> always the same.
Because those are release files and that's to edit history.
Jes
prev parent reply other threads:[~2020-05-14 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 13:27 [PATCH] Use more secure HTTPS URLs Paul Menzel
2020-05-13 13:44 ` Jes Sorensen
2020-05-14 20:39 ` Paul Menzel
2020-05-14 21:42 ` Jes Sorensen [this message]
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=e83921a0-fed5-be7f-e5ff-5a3f37cb53ec@gmail.com \
--to=jes.sorensen@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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).