From: "Brigham Campbell" <me@brighamcampbell.com>
To: "Randy Dunlap" <rdunlap@infradead.org>,
"Brigham Campbell" <me@brighamcampbell.com>,
"Thorsten Leemhuis" <linux@leemhuis.info>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"open list:DOCUMENTATION REPORTING ISSUES"
<linux-doc@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] docs: Fix minor grammatical error
Date: Mon, 08 Jun 2026 23:50:45 -0600 [thread overview]
Message-ID: <DJ4A839X388E.376Q6KVB6JE14@brighamcampbell.com> (raw)
In-Reply-To: <4c9b2927-29e0-40a6-bed4-14142dedd2ef@infradead.org>
On Sat Jun 6, 2026 at 1:10 PM MDT, Randy Dunlap wrote:
> Can't you just modify the first line only and leave the other 3 changed lines
> intact?
I'm not as familiar with the kernel documentation project as I am with
the code itself. I figured that it's generally preferred to maintain
80-character hard wrapping consistently across all documentation. Is it
actually preferable to _not_ reflow text after editing in order to avoid
munging the git history?
Thanks for your time, Randy,
Brigham
next prev parent reply other threads:[~2026-06-09 5:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 5:38 Brigham Campbell
2026-06-06 19:10 ` Randy Dunlap
2026-06-09 5:50 ` Brigham Campbell [this message]
2026-06-09 6:15 ` Thorsten Leemhuis
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=DJ4A839X388E.376Q6KVB6JE14@brighamcampbell.com \
--to=me@brighamcampbell.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®