From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Pereira <danielmaraboo@gmail.com>,
Daniel Castro <arantescastro@gmail.com>
Cc: linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] docs: pt_BR: translate process/1.Intro.rst
Date: Tue, 17 Mar 2026 11:00:29 -0600 [thread overview]
Message-ID: <875x6ubdci.fsf@trenco.lwn.net> (raw)
In-Reply-To: <CAMAsx6c_oq5-cuf-N-+RTo-Hym-K+PF-=BOBZySWMN4E7O1s4A@mail.gmail.com>
Daniel Pereira <danielmaraboo@gmail.com> writes:
> On Tue, Mar 17, 2026 at 11:02 AM Daniel Castro <arantescastro@gmail.com> wrote:
>>
> Thank you for sending the new version. Please review the following
> crucial points before submitting v3:
>
> New Email for Each Version: Always send patches in a new email,
> including the version number in the subject (e.g., [PATCH v3] docs:
> pt_BR: translate process/1.Intro.rst). This is vital for community
> tracking.
Daniel did mark v2 correctly. A new version definitely should be sent
as the start of a new thread, though, rather than as a reply to the
previous.
> Subheading Formatting: The misalignment in the subheading separators
> persists (e.g., +Créditos/+--------). Please correct this.
Looking at the patch:
> +
> +Créditos
> +--------
> +
>
...I don't see the problem you are describing here?
And again, please put comments like that inline, as I am doing here;
that makes it far easier for everybody to follow what's going on.
> Use checkpatch.pl: Always run the checkpatch.pl tool before
> submitting. This is mandatory and will catch these style errors,
> helping to prevent rejections.
Good advice, but checkpatch doesn't emit any actionable suggestions for
this patch...?
All told, I don't see a reason not to apply this version, is there
something I'm missing?
Thanks,
jon
next prev parent reply other threads:[~2026-03-17 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 21:24 [PATCH] docs: pt_BR: translate process/1.Intro.rst Daniel Castro
2026-03-16 22:59 ` Daniel Pereira
2026-03-16 23:55 ` Jonathan Corbet
2026-03-17 14:01 ` [PATCH v2] " Daniel Castro
2026-03-17 16:43 ` Daniel Pereira
2026-03-17 17:00 ` Jonathan Corbet [this message]
2026-03-17 17:16 ` Daniel Pereira
2026-03-22 20:47 ` Jonathan Corbet
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=875x6ubdci.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=arantescastro@gmail.com \
--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 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.