linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Alexander A. Klimov" <grandmaster@al2klimov.de>,
	santosh.shilimkar@oracle.com, davem@davemloft.net,
	kuba@kernel.org, netdev@vger.kernel.org,
	linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH for v5.9] RDS: Replace HTTP links with HTTPS ones
Date: Mon, 20 Jul 2020 17:07:16 +0300	[thread overview]
Message-ID: <20200720140716.GB1080481@unreal> (raw)
In-Reply-To: <20200720075848.26bc3dfe@lwn.net>

On Mon, Jul 20, 2020 at 07:58:48AM -0600, Jonathan Corbet wrote:
> On Mon, 20 Jul 2020 07:56:26 +0300
> Leon Romanovsky <leon@kernel.org> wrote:
>
> > >  Documentation/networking/rds.rst | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > Why can't it be done in one mega-patch?
> > It is insane to see patch for every file/link.
> >
> > We have more than 4k files with http:// in it.
>
> Do *you* want to review that megapatch?  The number of issues that have
> come up make it clear that these patches do, indeed, need review...

Can you point me to the issues?
What can go wrong with such a simple replacement?

I can review per-folder patches if it helps.

Thanks

>
> jon

  reply	other threads:[~2020-07-20 14:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-19 15:58 [PATCH for v5.9] RDS: Replace HTTP links with HTTPS ones Alexander A. Klimov
2020-07-20  4:56 ` Leon Romanovsky
2020-07-20 13:58   ` Jonathan Corbet
2020-07-20 14:07     ` Leon Romanovsky [this message]
2020-07-20 14:36       ` Jonathan Corbet
2020-07-20 16:48         ` Leon Romanovsky
2020-07-20 21:34           ` Alexander A. Klimov
2020-07-21  6:05             ` Leon Romanovsky
2020-07-21  6:43               ` Alexander A. Klimov
2020-07-21  8:54                 ` Leon Romanovsky

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=20200720140716.GB1080481@unreal \
    --to=leon@kernel.org \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=grandmaster@al2klimov.de \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rds-devel@oss.oracle.com \
    --cc=santosh.shilimkar@oracle.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).