From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, tglx@linutronix.de,
viro@zeniv.linux.org.uk
Subject: [RFC] Makefiles in scripts dir needs to move one place
Date: Mon, 30 Sep 2019 13:40:41 +0530 [thread overview]
Message-ID: <20190930081041.GA11886@Slackware> (raw)
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
Hey Greg ,
Absolute trivialities, but might break few scripts, but make things
clean..
We have so many *Makefile.* cluttering in the top level scripts dir.
Can we please move those in one place, means create a dir and put all
of them in it.
And call those in the scripts with that dir preceded . Kindly , let me
know how awful that would be.
Thanks,
Bhaskar
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-09-30 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 8:10 Bhaskar Chowdhury [this message]
2019-09-30 8:18 ` [RFC] Makefiles in scripts dir needs to move one place Greg KH
2019-09-30 14:26 ` Bhaskar Chowdhury
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=20190930081041.GA11886@Slackware \
--to=unixbhaskar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).