From: Paul Moore <paul@paul-moore.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: casey@schaufler-ca.com, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH] MAINTAINERS: git://github -> https://github.com for cschaufler
Date: Thu, 13 Oct 2022 17:54:00 -0400 [thread overview]
Message-ID: <CAHC9VhTPt40PFC5NASOjOK+fqJym5JOyb8UrwAL7DGDQWqVwqA@mail.gmail.com> (raw)
In-Reply-To: <20221013214637.30807-1-palmer@rivosinc.com>
On Thu, Oct 13, 2022 at 5:49 PM Palmer Dabbelt <palmer@rivosinc.com> wrote:
>
> Github deprecated the git:// links about a year ago, so let's move to
> the https:// URLs instead.
>
> Reported-by: Conor Dooley <conor.dooley@microchip.com>
> Link: https://github.blog/2021-09-01-improving-git-protocol-security-github/
> Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
> ---
> I've split these up by github username so folks can take them
> independently, as some of these repos have been renamed at github and
> thus need more than just a sed to fix them.
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Casey is the one who needs to ACK this (and he has an email delay at
the moment), but the URL looks good to me.
Reviewed-by: Paul Moore <paul@paul-moore.com>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index daadd0de77a9..019cdb48e254 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -18723,7 +18723,7 @@ M: Casey Schaufler <casey@schaufler-ca.com>
> L: linux-security-module@vger.kernel.org
> S: Maintained
> W: http://schaufler-ca.com
> -T: git git://github.com/cschaufler/smack-next
> +T: git https://github.com/cschaufler/smack-next
> F: Documentation/admin-guide/LSM/Smack.rst
> F: security/smack/
>
> --
> 2.38.0
--
paul-moore.com
next prev parent reply other threads:[~2022-10-13 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 21:46 [PATCH] MAINTAINERS: git://github -> https://github.com for cschaufler Palmer Dabbelt
2022-10-13 21:54 ` Paul Moore [this message]
2022-10-14 3:51 ` Palmer Dabbelt
2022-10-20 16:19 ` Casey Schaufler
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=CAHC9VhTPt40PFC5NASOjOK+fqJym5JOyb8UrwAL7DGDQWqVwqA@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=casey@schaufler-ca.com \
--cc=conor.dooley@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=palmer@rivosinc.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).