mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Pereira <danielmaraboo@gmail.com>
To: Lucas Adryell Ramalho <lucasadramalho@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	 Randy Dunlap <rdunlap@infradead.org>,
	linux-doc@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: translations: pt_BR: translate volatile-considered-harmful.rst
Date: Mon, 31 Aug 2026 09:37:26 -0300	[thread overview]
Message-ID: <CAMAsx6d458V3ByxwgP54mPvC6VZO2O8kBFjUiq-55r3UnhpKWQ@mail.gmail.com> (raw)
In-Reply-To: <20260830205912.478358-1-lucasadramalho@gmail.com>

Em dom., 30 de ago. de 2026 às 18:00, Lucas Adryell Ramalho
<lucasadramalho@gmail.com> escreveu:
>
> Translate volatile-considered-harmful.rst into Brazilian Portuguese and
> add it to the pt_BR process documentation index.
>
> Assisted-by: ChatGPT:GPT-5.5
> Signed-off-by: Lucas Adryell Ramalho <lucasadramalho@gmail.com>
> ---
>  .../translations/pt_BR/process/index.rst      |   1 +
>  .../process/volatile-considered-harmful.rst   | 130 ++++++++++++++++++
>  2 files changed, 131 insertions(+)
>  create mode 100644 Documentation/translations/pt_BR/process/volatile-considered-harmful.rst
>

Hi Lucas,

    I have reviewed the entire translation and it looks perfect. The technical
  terminology was very well adapted to Portuguese and the original meaning is
  fully preserved.

    I also ran checkpatch.pl and make htmldocs, and everything compiled smoothly
  without any errors. Excellent work!

    Reviewed-by: Daniel Pereira <danielmaraboo@gmail.com>

  reply	other threads:[~2026-08-31 12:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-30 20:59 Lucas Adryell Ramalho
2026-08-31 12:37 ` Daniel Pereira [this message]
2026-09-07 16:50 ` Jonathan Corbet

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=CAMAsx6d458V3ByxwgP54mPvC6VZO2O8kBFjUiq-55r3UnhpKWQ@mail.gmail.com \
    --to=danielmaraboo@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucasadramalho@gmail.com \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.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

all inboxes | Powered by JetHome®