linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Sanjeev Gupta <ghane0@gmail.com>, linux-doc@vger.kernel.org
Cc: Sanjeev Gupta <ghane0@gmail.com>,
	Federico Vaga <federico.vaga@vaga.pv.it>,
	Alex Shi <alexs@kernel.org>,
	Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [PATCH v2 1/3] Documentation/translations/it_IT: switch LWN links to https
Date: Thu, 20 May 2021 14:18:38 -0600	[thread overview]
Message-ID: <87fsyhnopt.fsf@meer.lwn.net> (raw)
In-Reply-To: <743d9c7f.AUwAAC8yN1IAAAAAAAAAAKAiBu8AAAAAAMcAAAAAAA6qeABgn302@mailjet.com>

Sanjeev Gupta <ghane0@gmail.com> writes:

> Links have been checked to ensure that the old and new URL
> return the same page.
>
> Signed-off-by: Sanjeev Gupta <ghane0@gmail.com>
> ---
>  Documentation/translations/it_IT/process/2.Process.rst      | 2 +-
>  Documentation/translations/it_IT/process/3.Early-stage.rst  | 4 ++--
>  Documentation/translations/it_IT/process/4.Coding.rst       | 2 +-
>  .../translations/it_IT/process/7.AdvancedTopics.rst         | 2 +-
>  Documentation/translations/it_IT/process/8.Conclusion.rst   | 6 +++---
>  .../it_IT/process/volatile-considered-harmful.rst           | 4 ++--
>  6 files changed, 10 insertions(+), 10 deletions(-)

So these seem about ready to apply, but ... they never made it to a
public list.  I see linux-doc in the headers, but somehow your messages
didn't actually get there.

Could I ask you to resend, fixing whatever it was that prevented the
messages from getting onto linux-doc last time?  While you are at it,
you can also send them as a proper series with a cover letter and fix
the additional URL that Federico pointed out in part 2.

Thanks,

jon

           reply	other threads:[~2021-05-20 20:18 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <743d9c7f.AUwAAC8yN1IAAAAAAAAAAKAiBu8AAAAAAMcAAAAAAA6qeABgn302@mailjet.com>]

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=87fsyhnopt.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=alexs@kernel.org \
    --cc=federico.vaga@vaga.pv.it \
    --cc=ghane0@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    /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).