mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: tony.luck@intel.com, fenghua.yu@intel.com,
	linux-ia64@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ia64: Replace HTTP links with HTTPS ones
Date: Thu, 23 Jul 2020 14:47:25 -0600	[thread overview]
Message-ID: <20200723144725.17e369e0@lwn.net> (raw)
In-Reply-To: <20200713215506.44327-1-grandmaster@al2klimov.de>

On Mon, 13 Jul 2020 23:55:06 +0200
"Alexander A. Klimov" <grandmaster@al2klimov.de> wrote:

>  Documentation/ia64/xen.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/ia64/xen.rst b/Documentation/ia64/xen.rst
> index 831339c74441..9da6abb02a2c 100644
> --- a/Documentation/ia64/xen.rst
> +++ b/Documentation/ia64/xen.rst
> @@ -28,7 +28,7 @@ Getting and Building Xen and Dom0
>  
>  	# hg clone http://xenbits.xensource.com/ext/ia64/xen-unstable.hg
>  	# cd xen-unstable.hg
> -	# hg clone http://xenbits.xensource.com/ext/ia64/linux-2.6.18-xen.hg
> +	# hg clone https://xenbits.xensource.com/ext/ia64/linux-2.6.18-xen.hg
>  
>   2. # make world

So ... this is a sequence of operations that clearly cannot work at all
since the repo link you didn't change is broken.  And if it were to
somehow work, we'd get ... a 2.6.18 version of ia64 xen?  I think that the
proper solution here is to simply delete this document...

jon

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13 14:10 [PATCH] " Alexander A. Klimov
2020-07-13 14:34 ` Jonathan Corbet
2020-07-13 21:55   ` [PATCH v2] " Alexander A. Klimov
2020-07-23 20:47     ` Jonathan Corbet [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=20200723144725.17e369e0@lwn.net \
    --to=corbet@lwn.net \
    --cc=fenghua.yu@intel.com \
    --cc=grandmaster@al2klimov.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.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

all inboxes | Powered by JetHome®