All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Pereira <danielmaraboo@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Subject: [PATCH v1 2/3] docs: translations: pt_BR: use plain filenames in process index
Date: Mon, 16 Nov 2026 08:56:04 -0300	[thread overview]
Message-ID: <20261116115605.174735-3-danielmaraboo@gmail.com> (raw)
In-Reply-To: <20261116115605.174735-1-danielmaraboo@gmail.com>

- index: list entries by filename only, as in the English original,
  so titles come from each document and cannot go out of sync.
- index: drop ".rst" from contribution-maturity-model and fix the
  4-space indentation.
- howto: "COMO FAZER" -> "Como fazer". The title now shows in the
  index and was the only one in upper case.

Signed-off-by: Daniel Pereira <danielmaraboo@gmail.com>
---
 .../translations/pt_BR/process/howto.rst      |  2 +-
 .../translations/pt_BR/process/index.rst      | 74 +++++++++----------
 2 files changed, 38 insertions(+), 38 deletions(-)

diff --git a/Documentation/translations/pt_BR/process/howto.rst b/Documentation/translations/pt_BR/process/howto.rst
index 6f0b3cd9d..db263f89e 100644
--- a/Documentation/translations/pt_BR/process/howto.rst
+++ b/Documentation/translations/pt_BR/process/howto.rst
@@ -2,7 +2,7 @@
 
 .. _pt_process_howto:
 
-COMO FAZER o desenvolvimento do kernel Linux
+Como fazer o desenvolvimento do kernel Linux
 ============================================
 
 Este é o documento definitivo sobre este tópico. Ele contém instruções
diff --git a/Documentation/translations/pt_BR/process/index.rst b/Documentation/translations/pt_BR/process/index.rst
index da92a7026..689117ad9 100644
--- a/Documentation/translations/pt_BR/process/index.rst
+++ b/Documentation/translations/pt_BR/process/index.rst
@@ -24,10 +24,10 @@ sua entrada na comunidade do kernel.
 .. toctree::
    :maxdepth: 1
 
-   Como começar <howto>
-   Guia do Processo de Desenvolvimento <development-process>
-   Enviando patches: o guia essencial para colocar o seu código no kernel <submitting-patches>
-   Lista de verificação para submissão de patches do kernel Linux <submit-checklist>
+   howto
+   development-process
+   submitting-patches
+   submit-checklist
 
 Ferramentas e guias técnicos para desenvolvedores do kernel
 -----------------------------------------------------------
@@ -38,16 +38,16 @@ devem estar familiarizados.
 .. toctree::
    :maxdepth: 1
 
-   Requisitos mínimos <changes>
-   Linguagem de programação <programming-language>
-   Estilo de codificação do kernel Linux <coding-style>
-   Guia PGP para mantenedores do kernel <maintainer-pgp-guide>
-   Informações sobre clientes de email para Linux <email-clients>
-   Como aplicar patches <applying-patches>
-   Backporting e resolução de conflitos <backporting>
-   Adicionando uma nova chamada de Sistema <adding-syscalls>
-   Por que a classe de tipo "volatile" não deve ser usada <volatile-considered-harmful>
-   Como não Deixar as ioctls malfeitas <botching-up-ioctls>
+   changes
+   programming-language
+   coding-style
+   maintainer-pgp-guide
+   email-clients
+   applying-patches
+   backporting
+   adding-syscalls
+   volatile-considered-harmful
+   botching-up-ioctls
 
 Guias de políticas e declarações de desenvolvedores
 ---------------------------------------------------
@@ -58,17 +58,17 @@ Estas são as regras pelas quais tentamos viver na comunidade do kernel
 .. toctree::
    :maxdepth: 1
 
-   Regras de licenciamento <license-rules>
-   Código de Conduta de Compromisso do Colaborador <code-of-conduct>
-   Interpretação do Código de Conduta do Kernel Linux <code-of-conduct-interpretation>
-   Modelos de Maturidade para Contribuição no Kernel Linux <contribution-maturity-model.rst>
-   Declaração de Aplicação do Kernel Linux <kernel-enforcement-statement>
-   Declaração sobre Drivers do Kernel <kernel-driver-statement>
-   A interface de drivers do kernel Linux <stable-api-nonsense>
-   Estilo de gerenciamento do kernel Linux <management-style>
-   Assistentes de código <coding-assistants>
-   O manual da árvore tip <maintainer-tip>
-   Conclave (Continuidade do projeto) <conclave>
+   license-rules
+   code-of-conduct
+   code-of-conduct-interpretation
+   contribution-maturity-model
+   kernel-enforcement-statement
+   kernel-driver-statement
+   stable-api-nonsense
+   management-style
+   coding-assistants
+   maintainer-tip
+   conclave
 
 Lidando com bugs
 ----------------
@@ -80,10 +80,10 @@ gerenciamento de bugs e vulnerabilidades.
 .. toctree::
    :maxdepth: 1
 
-   Dicas de depuração para desenvolvedores do Kernel Linux <debugging/index>
-   Falhas de segurança <security-bugs>
-   Problemas de hardware sob embargo <embargoed-hardware-issues>
-   CVEs <cve>
+   debugging/index
+   security-bugs
+   embargoed-hardware-issues
+   cve
 
 Informações para mantenedores
 -----------------------------
@@ -94,12 +94,12 @@ mantenedores de subsistemas.
 .. toctree::
    :maxdepth: 1
 
-   Manuais dos mantenedores <maintainer-handbooks>
-   Processo do subsistema de rede (netdev) <maintainer-netdev>
-   Processo do subsistema SoC <maintainer-soc>
-   Conformidade de DTS para SoC <maintainer-soc-clean-dts>
-   Processo do subsistema KVM x86 <maintainer-kvm-x86>
-   Subsistema de Devicetree e Open Firmware <maintainer-devicetree>
+   maintainer-handbooks
+   maintainer-netdev
+   maintainer-soc
+   maintainer-soc-clean-dts
+   maintainer-kvm-x86
+   maintainer-devicetree
 
 Outros materiais
 ----------------
@@ -110,5 +110,5 @@ a maioria dos desenvolvedores:
 .. toctree::
    :maxdepth: 1
 
-   Index de documentos do Kernel <kernel-docs>
-   Interfaces, recursos de linguagem, atributos e convenções obsoletos <deprecated>
+   kernel-docs
+   deprecated
-- 
2.56.0


  parent reply	other threads:[~2026-11-16 11:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 11:56 [PATCH v1 0/3] docs: translations: pt_BR: wording fixes and plain process index Daniel Pereira
2026-11-16 11:56 ` [PATCH v1 1/3] docs: translations: pt_BR: fix wording in index, disclaimer and howto Daniel Pereira
2026-11-16 11:56 ` Daniel Pereira [this message]
2026-11-16 11:56 ` [PATCH v1 3/3] docs: translations: pt_BR: use "branch" instead of "ramo" Daniel Pereira

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=20261116115605.174735-3-danielmaraboo@gmail.com \
    --to=danielmaraboo@gmail.com \
    --cc=corbet@lwn.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.