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: Re: [RFC] Makefiles in scripts dir needs to move one place
Date: Mon, 30 Sep 2019 19:56:48 +0530 [thread overview]
Message-ID: <20190930142648.GA30066@Slackware> (raw)
In-Reply-To: <20190930081816.GA2036553@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
On 10:18 Mon 30 Sep 2019, Greg KH wrote:
>On Mon, Sep 30, 2019 at 01:40:41PM +0530, Bhaskar Chowdhury wrote:
>>
>> 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.
>
>Why? What would that help with?
>
Cleanliness of that directory. Nothing else,kinda organized way.YMMV
>> And call those in the scripts with that dir preceded . Kindly , let me
>> know how awful that would be.
>
>I can not parse these sentances, sorry.
>
:) All , I was trying to say that , the path to the makefile inside the
scripts will add that directory to the existing path.
Say, present is like /foo/bar/hoo that will become /foo/moo/bar/hoo
that "moo" directory will holds all the makefiles.
Okay, as I said ,in top of the mail this is absolute trivialities.
Bhaskar
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-09-30 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 8:10 [RFC] Makefiles in scripts dir needs to move one place Bhaskar Chowdhury
2019-09-30 8:18 ` Greg KH
2019-09-30 14:26 ` Bhaskar Chowdhury [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=20190930142648.GA30066@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 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.