From: Jakub Kicinski <kuba@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, sean.anderson@seco.com, corbet@lwn.net,
linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next] docs: netdev: add note about Changes Requested and revising commit messages
Date: Wed, 22 Mar 2023 18:06:57 -0700 [thread overview]
Message-ID: <20230322180657.41903d30@kernel.org> (raw)
In-Reply-To: <af2e9958-d624-d5fc-9403-a082ff15df9a@infradead.org>
On Wed, 22 Mar 2023 16:38:53 -0700 Randy Dunlap wrote:
> > +had to ask in previous discussions. Occasionally the update of
>
> asked in previous discussions.
"had to ask" as in were forced to ask due to a poor commit message,
is that not a valid use of "had to"?
next prev parent reply other threads:[~2023-03-23 1:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 23:12 [PATCH net-next] docs: netdev: add note about Changes Requested and revising commit messages Jakub Kicinski
2023-03-22 23:38 ` Randy Dunlap
2023-03-23 1:06 ` Jakub Kicinski [this message]
2023-03-23 1:11 ` Randy Dunlap
2023-03-24 5:00 ` patchwork-bot+netdevbpf
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=20230322180657.41903d30@kernel.org \
--to=kuba@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=sean.anderson@seco.com \
/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).