linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robby Workman <rworkman@slackware.com>
To: Lucas De Marchi <lucas.de.marchi@gmail.com>
Cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	linux-modules <linux-modules@vger.kernel.org>
Subject: Re: [kmod] Fix typo
Date: Tue, 22 Jan 2019 17:25:22 -0800 (PST)	[thread overview]
Message-ID: <alpine.LNX.2.02.1901221724180.24744@connie.slackware.com> (raw)
In-Reply-To: <CAKi4VAJQ_XjwcoAFCwT0x9aZMWAvNQ4OuMcEax8OALP4fqS6dA@mail.gmail.com>

On Tue, 22 Jan 2019, Lucas De Marchi wrote:

> On Mon, Jan 14, 2019 at 12:32 PM Daniel Kahn Gillmor
> <dkg@fifthhorseman.net> wrote:
>>
>> On Sat 2019-01-12 13:59:47 -0800, Robby Workman wrote:
>>> I *think* that was supposed to be "of any files" when it was originally
>>> typed, but either works, I suppose :-)
>>
>> I'm fine however it gets resolved -- just please don't leave it with the
>> broken text.
>
> a little bit of archaeology:
>
> this line originally came from the module-init-tools' man page written
> in "doc/modprobe.conf.sgml".
> Grepping that repo shows that it probably was a copy of
> doc/depmod.conf.sgml that
> had phrase "The format of <filename>depmod.conf</filename> and files
> under <filename>depmod.d</filename> is simple"
>
> So, whoever copied it over forgot to remove the "and". Not that any of
> this matter... your version or the
> other are perfectly fine today :)


Yeah, oops here. I called myself proofing all of that as I copied it,
and I made quite a few changes along the way, but oh well. 
Thanks Daniel and Lucas :-)

-RW

      reply	other threads:[~2019-01-23  1:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-12 17:22 [kmod] Fix typo Daniel Kahn Gillmor
2019-01-12 21:59 ` Robby Workman
2019-01-14 19:59   ` Daniel Kahn Gillmor
2019-01-22 22:12     ` Lucas De Marchi
2019-01-23  1:25       ` Robby Workman [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=alpine.LNX.2.02.1901221724180.24744@connie.slackware.com \
    --to=rworkman@slackware.com \
    --cc=dkg@fifthhorseman.net \
    --cc=linux-modules@vger.kernel.org \
    --cc=lucas.de.marchi@gmail.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).