Subsystems (2)
Daniel Pereira
maintainerSubject: [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.
Thanks!
Daniel Pereira (4):
docs: pt_BR: Translate submit-checklist to Portuguese
docs: pt_BR: Translate code-of-conduct-interpretation to Portuguese
docs: pt_BR: Translate Code of Conduct to Portuguese
docs: pt_BR: Translate deprecated interfaces guide to Portuguese
Documentation/translations/pt_BR/index.rst | 5 + .../code-of-conduct-interpretation.rst | 257 +++++++++++ .../pt_BR/process/code-of-conduct.rst | 88 ++++ .../translations/pt_BR/process/deprecated.rst | 422 ++++++++++++++++++ .../pt_BR/process/submit-checklist.rst | 145 ++++++ 5 files changed, 917 insertions(+) create mode 100644 Documentation/translations/pt_BR/process/code-of-conduct-interpretation.rst create mode 100644 Documentation/translations/pt_BR/process/code-of-conduct.rst create mode 100644 Documentation/translations/pt_BR/process/deprecated.rst create mode 100644 Documentation/translations/pt_BR/process/submit-checklist.rst
Signature · 1 line
2.47.3
Daniel Pereira
maintainerPATCH 1/4 docs: pt_BR: Translate submit-checklist to Portuguese
Translate the submit-checklist document from Documentation/process/ to Portuguese (pt_BR) to make the kernel contribution guidelines more accessible to Portuguese-speaking developers.
Also, add the newly translated file to the main index in the pt_BR translation directory to ensure it compiles and links correctly within the Sphinx build.
--- Documentation/translations/pt_BR/index.rst | 1 + .../pt_BR/process/submit-checklist.rst | 145 ++++++++++++++++++ 2 files changed, 146 insertions(+) create mode 100644 Documentation/translations/pt_BR/process/submit-checklist.rst
Documentation/translations/pt_BR/index.rst +1 -0
@@ -83,3 +83,4 @@ kernel e sobre como ver seu trabalho integrado. Conformidade de DTS para SoC <process/maintainer-soc-clean-dts> Processo do subsistema KVM x86 <process/maintainer-kvm-x86> Adicionando uma nova chamada de Sistema <process/adding-syscalls> + Lista de verificação para submissão de patches do kernel Linux <process/submit-checklist>
Documentation/translations/pt_BR/process/submit-checklist.rst new file +145 -0
145 lines not on this page · raw message
Signature · 1 line
2.47.3
Daniel Pereira
maintainerPATCH 2/4 docs: pt_BR: Translate code-of-conduct-interpretation to Portuguese
In reply to Daniel PereiraTranslate the code-of-conduct-interpretation.rst document from Documentation/process/ to Portuguese (pt_BR) to make the kernel guidelines on community standards and enforcement more accessible to Portuguese-speaking developers.
--- Documentation/translations/pt_BR/index.rst | 1 + .../code-of-conduct-interpretation.rst | 257 ++++++++++++++++++ 2 files changed, 258 insertions(+) create mode 100644 Documentation/translations/pt_BR/process/code-of-conduct-interpretation.rst
Documentation/translations/pt_BR/index.rst +1 -0
@@ -84,3 +84,4 @@ kernel e sobre como ver seu trabalho integrado. Processo do subsistema KVM x86 <process/maintainer-kvm-x86> Adicionando uma nova chamada de Sistema <process/adding-syscalls> Lista de verificação para submissão de patches do kernel Linux <process/submit-checklist> + Interpretação do Código de Conduta do Kernel Linux <process/code-of-conduct-interpretation>
Documentation/translations/pt_BR/process/code-of-conduct-interpretation.rst new file +257 -0
258 lines not on this page · raw message
Signature · 1 line
2.47.3
Daniel Pereira
maintainerPATCH 3/4 docs: pt_BR: Translate Code of Conduct to Portuguese
In reply to Daniel PereiraTranslate the Contributor Covenant Code of Conduct document from Documentation/process/code-of-conduct.rst to Portuguese (pt_BR) to ensure the community guidelines are accessible in the local language.
Also, add the newly translated file to the main index in the pt_BR translation directory to ensure it compiles correctly within the Sphinx build.
--- Documentation/translations/pt_BR/index.rst | 3 + .../pt_BR/process/code-of-conduct.rst | 88 +++++++++++++++++++ 2 files changed, 91 insertions(+) create mode 100644 Documentation/translations/pt_BR/process/code-of-conduct.rst
Documentation/translations/pt_BR/index.rst +3 -0
@@ -85,3 +85,6 @@ kernel e sobre como ver seu trabalho integrado. Adicionando uma nova chamada de Sistema <process/adding-syscalls> Lista de verificação para submissão de patches do kernel Linux <process/submit-checklist> Interpretação do Código de Conduta do Kernel Linux <process/code-of-conduct-interpretation> + Código de Conduta de Compromisso do Colaborador <process/code-of-conduct> + +
Documentation/translations/pt_BR/process/code-of-conduct.rst new file +88 -0
88 lines not on this page · raw message
Signature · 1 line
2.47.3
Daniel Pereira
maintainerPATCH 4/4 docs: pt_BR: Translate deprecated interfaces guide to Portuguese
In reply to Daniel PereiraTranslate the deprecated interfaces, language features, attributes, and conventions document (deprecated.rst) to Portuguese (pt_BR).
This ensures Portuguese-speaking developers have access to local guidelines on deprecated APIs (like BUG(), strcpy(), and VLAs), correct usage of safe alternatives (like WARN(), strscpy(), and flexible array members), and modern object allocator macros (kmalloc_obj).
--- Documentation/translations/pt_BR/index.rst | 2 +- .../translations/pt_BR/process/deprecated.rst | 422 ++++++++++++++++++ 2 files changed, 423 insertions(+), 1 deletion(-) create mode 100644 Documentation/translations/pt_BR/process/deprecated.rst
Documentation/translations/pt_BR/index.rst +1 -1
@@ -86,5 +86,5 @@ kernel e sobre como ver seu trabalho integrado. Lista de verificação para submissão de patches do kernel Linux <process/submit-checklist> Interpretação do Código de Conduta do Kernel Linux <process/code-of-conduct-interpretation> Código de Conduta de Compromisso do Colaborador <process/code-of-conduct> - + Interfaces, recursos de linguagem, atributos e convenções obsoletos <process/deprecated>
Documentation/translations/pt_BR/process/deprecated.rst new file +422 -0
422 lines not on this page · raw message
Signature · 1 line
2.47.3
Daniel Pereira
maintainerEm qua., 15 de jul. de 2026 às 23:10, Daniel Pereira <[email protected]> escreveu:
Quoted 3 lines
Subject: [PATCH 0/4] doc:
pt_BR: Add translations for process and guidelines
Hello Corbet,
I am writing to apologize for a formatting issue in my recent patch submission. I mistakenly included an extra space when generating the cover letter, which caused the title to be omitted.
Please let me know if you would like me to send a v2 of the patch series with this corrected. I am happy to address this immediately if needed.
Best regards,
Daniel Pereira
Jonathan Corbet
maintainerQuoted 8 lines · Daniel Pereira
Em qua., 15 de jul. de 2026 às 23:10, Daniel Pereira <[email protected]> escreveu:
Quoted 3 lines
Subject: [PATCH 0/4] doc:
pt_BR: Add translations for process and guidelinesHello Corbet,
Quoted 7 lines
I am writing to apologize for a formatting issue in my recent patch submission. I mistakenly included an extra space when generating the cover letter, which caused the title to be omitted.
Please let me know if you would like me to send a v2 of the patch series with this corrected. I am happy to address this immediately if needed.
No need to do that.
Thanks,
jon
Quoted 14 lines · Daniel Pereira
Subject: [PATCH 0/4] doc:
pt_BR: Add translations for process and guidelinesHello,
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.
Quoted 4 lines
All files have been formatted to respect the 80-character line limit and the main
index.rsthas 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
Daniel Pereira
maintainerEm qui., 16 de jul. de 2026 às 19:50, Jonathan Corbet <[email protected]> escreveu:
Quoted 11 lines
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 theindex.rststructure 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.
Quoted 3 lines
Thanks,
jon
Hi Jon,
Thank you for the guidance on managing the index.rst structure.
Regarding the conflict issue, I would be happy to take on the responsibility of organizing these patches to help save you time. Would you prefer if I acted as a point of contact for these translations? I could collect submissions from contributors, merge them into the structure correctly, and then send them to you as a single, cleaned-up set of patches.
Please let me know if this workflow would be helpful or if you have a different preference for how I should handle these conflicts.
Best regards,
Jonathan Corbet
maintainerQuoted 9 lines · Daniel Pereira
Regarding the conflict issue, I would be happy to take on the responsibility of organizing these patches to help save you time. Would you prefer if I acted as a point of contact for these translations? I could collect submissions from contributors, merge them into the structure correctly, and then send them to you as a single, cleaned-up set of patches.
Please let me know if this workflow would be helpful or if you have a different preference for how I should handle these conflicts.
I think that if you organize the index.rst files as I suggested (i.e. roughly along the lines of the English versions) most of the conflicts will go away, and the result will better generally. That's the best place to start, I think.
Thanks,
jon
Daniel Pereira
maintainerEm sex., 17 de jul. de 2026 às 10:08, Jonathan Corbet <[email protected]> escreveu:
Quoted 9 lines
I think that if you organize the
index.rstfiles as I suggested (i.e. roughly along the lines of the English versions) most of the conflicts will go away, and the result will better generally. That's the best place to start, I think.Thanks,
jon
Hi Jon,
I’ve noticed a large volume of new contributions for the pt_BR translations recently.
To avoid conflicts during this integration period, could I keep the index.rst as it is until these recent patches are applied? Once everything is processed, I will make the adjustments to the structure to follow the organization of the English documentation as you suggested.
Thanks,
Daniel
Jonathan Corbet
maintainerQuoted 8 lines · Daniel Pereira
I’ve noticed a large volume of new contributions for the
pt_BRtranslations recently.To avoid conflicts during this integration period, could I keep the
index.rstas it is until these recent patches are applied? Once everything is processed, I will make the adjustments to the structure to follow the organization of the English documentation as you suggested.
In the end, you are in charge of that translation. I do ask translations to follow the structure of the English docs, but I'll let the maintainer decide the best way to get there.
Thanks,
jon