From: Brian Norris <briannorris@chromium.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Nicholas Mc Guire <der.herr@hofr.at>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [DOC] Missing completions-design.txt?
Date: Tue, 25 Oct 2016 12:50:01 -0700 [thread overview]
Message-ID: <20161025195000.GA17604@localhost> (raw)
Hi,
It looks like Nicholas submitted this doc a while back as patch 2/2:
"[PATCH 2/2] doc: detailed documentation for completion"
http://lkml.iu.edu/hypermail/linux/kernel/1412.2/03676.html
where patch 1/2 got merged as this:
202799be447b doc: brief user documentation for completion
References in the introduced completion.txt doc have pointed lost souls
at an elusive completion-design.txt:
"for details on completion design and implementation see
completions-design.txt"
Since as we well know, most developers are religious readers of
documentation, presumably there are people out there waiting expectantly
for such a file to appear in their otherwise exhaustive Documentation/.
Can you help such lost souls out?
Thanks,
Brian
P.S. I haven't actually read the design doc that closely yet. Who would
trust such a random patch off the archives, after all? So just removing
the mention of this file might be a satisfactory solution.
next reply other threads:[~2016-10-25 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 19:50 Brian Norris [this message]
2016-10-26 10:11 ` [DOC] Missing completions-design.txt? Nicholas Mc Guire
2016-11-15 22:42 ` [PATCH] docs/completion.txt: drop dangling reference to completions-design.txt Brian Norris
2016-11-16 23:28 ` 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=20161025195000.GA17604@localhost \
--to=briannorris@chromium.org \
--cc=corbet@lwn.net \
--cc=der.herr@hofr.at \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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.