From: Brian Gerst <bgerst@didntduck.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andrew Morton <akpm@osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Move modpost files to a new subdir [1/2]
Date: Fri, 23 Jul 2004 09:43:59 -0400 [thread overview]
Message-ID: <4101161F.3060905@didntduck.org> (raw)
In-Reply-To: <20040723151630.GA6914@mars.ravnborg.org>
Sam Ravnborg wrote:
> On Thu, Jul 22, 2004 at 08:43:57AM -0400, Brian Gerst wrote:
>
>>This patch simply moves modpost-related files to a seperate subdirectory.
>
>
> I did this in my local tree but decided for a different directory name.
> Usage of modpost would conflict with the modpost binary and I suspected
> that some systems would not allow this clash.
> I do not expect people to run make mrproper before applying a patch..
>
> The new directory name is: scripts/mod - also signalling that this can be
> used for other module related utilities in the future.
>
> Sam
>
scripts/modules would be more descriptive.
--
Brian Gerst
prev parent reply other threads:[~2004-07-23 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 12:43 [PATCH] Move modpost files to a new subdir [1/2] Brian Gerst
2004-07-23 15:16 ` Sam Ravnborg
2004-07-23 13:43 ` Brian Gerst [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=4101161F.3060905@didntduck.org \
--to=bgerst@didntduck.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox