Linux Documentation
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Pereira <danielmaraboo@gmail.com>
Cc: linux-doc@vger.kernel.org, Daniel Pereira <danielmaraboo@gmail.com>
Subject: Re: [PATCH 0/2] docs: pt_BR: Translate coding and posting guidelines
Date: Tue, 30 Jun 2026 13:56:49 -0600	[thread overview]
Message-ID: <87fr23reda.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260614235044.42810-1-danielmaraboo@gmail.com>

Daniel Pereira <danielmaraboo@gmail.com> writes:

> This patch series translates chapters 4 and 5 of the kernel development
> process documentation ("4.Coding.rst" and "5.Posting.rst") into 
> Brazilian Portuguese (pt_BR).
>
> The goal is to expand the available documentation for Portuguese-speaking
> developers, making it easier to understand core coding standards and
> patch submission guidelines.
>
> Daniel Pereira (2):
>   docs: pt_BR: Translate 4.coding.rst into Portuguese
>   docs: pt_BR: Translate patch posting documentation
>
>  .../translations/pt_BR/process/4.Coding.rst   | 440 ++++++++++++++++++
>  .../translations/pt_BR/process/5.Posting.rst  | 376 +++++++++++++++
>  .../pt_BR/process/development-process.rst     |   2 +
>  3 files changed, 818 insertions(+)
>  create mode 100644 Documentation/translations/pt_BR/process/4.Coding.rst
>  create mode 100644 Documentation/translations/pt_BR/process/5.Posting.rst

Applied, thanks.

jon

      parent reply	other threads:[~2026-06-30 19:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-14 23:50 [PATCH 0/2] docs: pt_BR: Translate coding and posting guidelines Daniel Pereira
2026-06-14 23:50 ` [PATCH 1/2] docs: pt_BR: Translate 4.coding.rst into Portuguese Daniel Pereira
2026-06-14 23:50 ` [PATCH 2/2] docs: pt_BR: Translate patch posting documentation Daniel Pereira
2026-06-29 16:27 ` [PATCH 0/2] docs: pt_BR: Translate coding and posting guidelines Daniel Pereira
2026-06-29 16:34   ` Jonathan Corbet
2026-06-30 19:56 ` 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=87fr23reda.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=danielmaraboo@gmail.com \
    --cc=linux-doc@vger.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