From: Yann Droneaud <ydroneaud@opteya.com>
To: linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
Michal Marek <mmarek@suse.cz>
Cc: Yann Droneaud <ydroneaud@opteya.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
David Woodhouse <dwmw2@infradead.org>,
Rob Landley <rob@landley.net>
Subject: [PATCHv1 0/2] Documentation: move and update headers_install.txt
Date: Sun, 13 Jul 2014 12:15:28 +0200 [thread overview]
Message-ID: <cover.1405246007.git.ydroneaud@opteya.com> (raw)
In-Reply-To: <20140709204915.GB32335@ravnborg.org>
On Wed, Jul 09, 2014 at 22:49 +0200, Sam Ravnborg wrote:
> On Thu, Jul 03, 2014 at 11:12:20PM +0200, Michal Marek wrote:
> > I have never noticed this file :). How about moving it to
> > Documentation/kbuild?
> Agree - please get this file moved.
>
Please find a patchset to move and update headers_install.txt.
Regards.
Yann Droneaud (2):
Documentation: headers_install.txt is part of kbuild
Documentation/kbuild/headers_install.txt: update documentation
Documentation/kbuild/00-INDEX | 2 ++
Documentation/{make => kbuild}/headers_install.txt | 15 ++++++++-------
2 files changed, 10 insertions(+), 7 deletions(-)
rename Documentation/{make => kbuild}/headers_install.txt (78%)
--
1.9.3
next prev parent reply other threads:[~2014-07-13 10:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 19:11 [PATCH] Documentation/make/headers_install.txt: update documentation Yann Droneaud
2014-07-03 21:12 ` Michal Marek
2014-07-09 20:49 ` Sam Ravnborg
2014-07-13 10:15 ` Yann Droneaud [this message]
2014-07-13 10:15 ` [PATCHv1 1/2] Documentation: headers_install.txt is part of kbuild Yann Droneaud
2014-07-13 21:18 ` Sam Ravnborg
2014-08-05 14:08 ` Michal Marek
2014-07-13 10:15 ` [PATCHv1 2/2] Documentation/kbuild/headers_install.txt: update documentation Yann Droneaud
2014-07-13 21:26 ` Sam Ravnborg
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=cover.1405246007.git.ydroneaud@opteya.com \
--to=ydroneaud@opteya.com \
--cc=dwmw2@infradead.org \
--cc=kirill@shutemov.name \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rob@landley.net \
--cc=sam@ravnborg.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.