From: Steven Rostedt <rostedt@goodmis.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
linux-mips@linux-mips.org, linux-fbdev@vger.kernel.org,
x86@kernel.org, kvm@vger.kernel.org, linux-doc@vger.kernel.org,
"Peter Zijlstra" <peterz@infradead.org>,
"James Hogan" <jhogan@kernel.org>,
"Henrik Austad" <henrik@austad.us>,
"Lai Jiangshan" <jiangshanlai@gmail.com>,
dri-devel@lists.freedesktop.org,
"Masahiro Yamada" <yamada.masahiro@socionext.com>,
"Jan Kandziora" <jjj@gmx.de>, "Paul Mackerras" <paulus@samba.org>,
"Henrik Austad" <haustad@cisco.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Evgeniy Polyakov" <zbr@ioremap.net>,
linux-s390@vger.kernel.org, "Ian Kent" <raven@themaw.net>,
linux-security-module@vger.kernel.org,
"Paul Moore" <paul@paul-moore.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Helge Deller" <deller@gmx.de>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"James E.J. Bottomley" <jejb@parisc-linux.or>
Subject: Re: [PATCH] [RFC v2] Drop all 00-INDEX files from Documentation/
Date: Tue, 4 Sep 2018 09:59:08 -0400 [thread overview]
Message-ID: <20180904095908.13298b3d@gandalf.local.home> (raw)
In-Reply-To: <20180904113030.GB25177@amd>
On Tue, 4 Sep 2018 13:30:30 +0200
Pavel Machek <pavel@ucw.cz> wrote:
> I'd say this is still quite valueable, and it might be worth fixing,
> rather then removing completely.
I agree. Perhaps we should have a 00-DESCRIPTION file in each
directory, and each file could start with a:
DESCRIPTION: <one line description here>
and then these files could be generated by those that have these tags.
-- Steve
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-09-04 13:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 22:15 [PATCH] [RFC v2] Drop all 00-INDEX files from Documentation/ Henrik Austad
2018-09-04 10:41 ` Mark Brown
2018-09-04 11:30 ` Pavel Machek
2018-09-04 13:59 ` Steven Rostedt [this message]
2018-09-06 15:58 ` Jonathan Corbet
2018-09-06 16:01 ` Steven Rostedt
2018-09-06 21:39 ` Daniel Vetter
2018-09-07 7:21 ` Greg Kroah-Hartman
2018-09-04 13:02 ` Paul E. McKenney
2018-09-04 15:45 ` Jens Axboe
2018-09-04 17:56 ` Mike Rapoport
2018-09-05 11:42 ` Paul Moore
2018-09-09 21:12 ` 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=20180904095908.13298b3d@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=corbet@lwn.net \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=haustad@cisco.com \
--cc=henrik@austad.us \
--cc=hpa@zytor.com \
--cc=jejb@parisc-linux.or \
--cc=jhogan@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=jjj@gmx.de \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mpe@ellerman.id.au \
--cc=paul@paul-moore.com \
--cc=paulus@samba.org \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=raven@themaw.net \
--cc=rkrcmar@redhat.com \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.com \
--cc=zbr@ioremap.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).