From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Pereira <danielmaraboo@gmail.com>, linux-doc@vger.kernel.org
Subject: Re: Question regarding CC list for pt_BR translation patches
Date: Mon, 13 Jul 2026 07:49:42 -0600 [thread overview]
Message-ID: <87fr1nhudl.fsf@trenco.lwn.net> (raw)
In-Reply-To: <CAMAsx6cLjU1N6zuM47KZcsRhq1ABvRZkw_y57szBHNe1o23tVw@mail.gmail.com>
Daniel Pereira <danielmaraboo@gmail.com> writes:
> Could you please clarify if you prefer to be CC'd on these translation
> patches, or is sending them solely to the mailing list sufficient for
> your review? I want to make sure we are following the community's best
> practices.
It's always best to CC the maintainer(s) directly. I do keep an eye on
the list, but the chances of something falling through the cracks are
higher if it is not sent to me directly as well.
Thanks,
jon
prev parent reply other threads:[~2026-07-13 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 12:58 Question regarding CC list for pt_BR translation patches Daniel Pereira
2026-07-13 13:49 ` 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=87fr1nhudl.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