From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Pereira <danielmaraboo@gmail.com>
Cc: linux-doc@vger.kernel.org
Subject: Re: [QUERY] Guidelines for starting pt_BR documentation translations
Date: Mon, 02 Feb 2026 10:27:17 -0700 [thread overview]
Message-ID: <87343jrr7u.fsf@trenco.lwn.net> (raw)
In-Reply-To: <CAMAsx6ehJD2b+2TFgqJ4VjE2=hfi4uW5j41A-MXg5YuBrbZ1AQ@mail.gmail.com>
Daniel Pereira <danielmaraboo@gmail.com> writes:
> Hello Jonathan,
>
> Thank you very much for your detailed response and the guidance. It's
> great to know we can move forward!
Next bit of guidance: avoid top-posting on kernel mailing lists; that
will irritate people quickly.
> I'd like to inform you that while I was waiting, I also translated the
> submitting-patches.rst file. I held off on sending it because I was
> waiting for your reply to ensure the initial procedure was correct.
>
> I am also pleased to share that I have a community of about 200
> students (I am a Linux instructor and systems engineer) who are
> willing to collaborate and maintain the pt_BR translation tree. This
> reinforces our commitment to ensuring the documentation remains
> up-to-date.
>
> My current question is regarding your observation about the merge
> window: Since I have already sent the first file (howto.rst), and with
> submitting-patches.rst ready, should I send the patch with the
> submitting-patches.rst translation now, or should I wait until the
> merge window is over, as you mentioned?
It's up to you; if you do send it, I'll end up stashing it aside for the
next few weeks.
Thanks,
jon
prev parent reply other threads:[~2026-02-02 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 0:23 [QUERY] Guidelines for starting pt_BR documentation translations Daniel Pereira
2026-02-02 15:51 ` Jonathan Corbet
2026-02-02 17:08 ` Daniel Pereira
2026-02-02 17:27 ` 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=87343jrr7u.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