From: Johannes Berg <johannes@sipsolutions.net>
To: Joe Perches <joe@perches.com>
Cc: Rob Landley <rob@landley.net>,
mm-commits@vger.kernel.org, fengguang.wu@intel.com,
linux-doc@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: docproc.c:
Date: Fri, 19 Jul 2013 08:42:39 +0300 [thread overview]
Message-ID: <e563de6dc20b7465431c19aa46d219cc@sipsolutions.net> (raw)
In-Reply-To: <1374199649.1949.143.camel@joe-AO722>
On 2013-07-19 05:07, Joe Perches wrote:
> These entries seem very arbitrary.
> (Also, I've never seen, nor cared about, them before)
>
> Any way to autogenerate this .tmpl file?
No way that I can think of that actually makes it simpler. Sure, you
could put a tag into each file and then use the tag, but what's the
point? The filename is also just a tag. Also, the tmpl files actually
contain content (if only just structure). I don't know which one links
printk.c, but look at other ones, e.g. the 802.11 one.
johannes
prev parent reply other threads:[~2013-07-19 6:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51e89d4a.EzMm4kY3e/JyyINM%akpm@linux-foundation.org>
2013-07-19 2:07 ` docproc.c: Joe Perches
2013-07-19 5:42 ` Johannes Berg [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=e563de6dc20b7465431c19aa46d219cc@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rob@landley.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