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:
Date: Thu, 16 Jul 2026 16:50:53 -0600 [thread overview]
Message-ID: <87ldba5z1u.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260716021013.48025-1-danielmaraboo@gmail.com>
Daniel Pereira <danielmaraboo@gmail.com> writes:
> Subject: [PATCH 0/4] doc: pt_BR: Add translations for process and guidelines
>
> Hello,
>
> This patch series adds the Brazilian Portuguese (pt_BR) translations for
> several essential files regarding community standards, submit checklists, and
> best development practices.
>
> Specifically, this series translates:
> 1. The submit-checklist guide.
> 2. The Code of Conduct interpretation document.
> 3. The core Contributor Covenant Code of Conduct.
> 4. The deprecated interfaces, attributes, and language features guide.
>
> All files have been formatted to respect the 80-character line limit and
> the main index.rst has been updated accordingly. The Sphinx documentation build
> (make htmldocs) compiles successfully with no warnings or errors related to
> these new files.
I've applied the series, thanks.
For future reference, a lot of the Portuguese translation patches are
giving me conflicts on Documentation/translations/pt_BR/index.rst. That
happens when you have a big file that everybody just appends to. Might
I request that you start managing the index.rst structure in the same
way as the English docs so that these additions are spread out and don't
conflict? That would also yield a more readable result for the
translation.
Thanks,
jon
next prev parent reply other threads:[~2026-07-16 22:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 2:10 Daniel Pereira
2026-07-16 2:10 ` [PATCH 1/4] docs: pt_BR: Translate submit-checklist to Portuguese Daniel Pereira
2026-07-16 2:10 ` [PATCH 2/4] docs: pt_BR: Translate code-of-conduct-interpretation " Daniel Pereira
2026-07-16 2:10 ` [PATCH 3/4] docs: pt_BR: Translate Code of Conduct " Daniel Pereira
2026-07-16 2:10 ` [PATCH 4/4] docs: pt_BR: Translate deprecated interfaces guide " Daniel Pereira
2026-07-16 3:54 ` Daniel Pereira
2026-07-16 14:37 ` Re: Jonathan Corbet
2026-07-16 22:50 ` Jonathan Corbet [this message]
2026-07-16 23:25 ` Re: Daniel Pereira
-- strict thread matches above, loose matches on Subject: below --
2025-08-18 16:08 [PATCH] documentation/arm64 : kdump fixed typo errors Jonathan Corbet
2025-09-08 9:54 ` hariconscious
2025-09-08 13:23 ` Jonathan Corbet
2019-02-18 23:41 Re: Pablo Mancilla
2018-12-04 2:28 RE, Ms Sharifah Ahmad Mustahfa
2018-11-24 14:19 RE, Miss Sharifah Ahmad Mustahfa
2018-11-24 14:16 RE, Miss Sharifah Ahmad Mustahfa
2018-11-24 14:16 RE, Miss Sharifah Ahmad Mustahfa
2018-11-24 14:03 RE, Miss Sharifah Ahmad Mustahfa
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=87ldba5z1u.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