From: Josh Soref <jsoref@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/1] Spelling code fixes*
Date: Wed, 12 Jan 2022 07:48:56 -0500 [thread overview]
Message-ID: <CACZqfqAZ9sp3R4f2gPhTET75=AnrzfG3Sxd4a1aSfKsMOSndgA@mail.gmail.com> (raw)
In-Reply-To: <5763376.alqRGMn8q6@thomas>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
On Wed, Jan 12, 2022, 6:50 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> 12/01/2022 08:28, Josh Soref:
> > fixed spellings:
> >
> > * accelerator
> > * acceptable
> > * account
> > * accounting
> > * acknowledge
> > * acknowledgement
> > * across
> > * action
> > * actually
> > * adapter
> > * adaptive
> > * added
> > * addition
> > * address
> > * addresses
> > * adds
> > * adjustment
> > * affinity
> ...
>
> It would be more convenient to review the changes, example:
> * acelerator -> accelerator
> And it would be nice to make some categories,
> like shorter and longer replacement,
> because shorter is almost always a good fix,
> but a longer replacement may not be required and require more attention.
>
The original task actually has this. But I generally fold all of the
replacements together, so a given commit for `addresses` at this point may
be a mix of changes from `addresse`, `adddresses`, and `Addressses`
[-- Attachment #2: Type: text/html, Size: 1417 bytes --]
prev parent reply other threads:[~2022-01-12 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 7:28 Josh Soref
2022-01-12 7:28 ` [PATCH 1/1] fix spelling in code Josh Soref
2022-01-12 11:46 ` Thomas Monjalon
2022-01-12 11:49 ` [PATCH 0/1] Spelling code fixes* Thomas Monjalon
2022-01-12 12:48 ` Josh Soref [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='CACZqfqAZ9sp3R4f2gPhTET75=AnrzfG3Sxd4a1aSfKsMOSndgA@mail.gmail.com' \
--to=jsoref@gmail.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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;
as well as URLs for NNTP newsgroup(s).