Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jike Song <albcamus@gmail.com>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: Do we really need file `all'?
Date: Tue, 30 Dec 2008 10:24:01 +0100	[thread overview]
Message-ID: <20081230092401.GB27321@uranus.ravnborg.org> (raw)
In-Reply-To: <df9815e70812292336h613585f2i217eeff47a6a9f2e@mail.gmail.com>

On Tue, Dec 30, 2008 at 03:36:19PM +0800, Jike Song wrote:
> On Tue, Dec 30, 2008 at 2:17 PM, Jike Song <albcamus@gmail.com> wrote:
> > Hi Sam,
> >
> >  In commit a680eedc6c621c75695c68198533fc3c98f4053b you introduced the
> > following code:
> >
> >        exuberant()
> >        {
> >                all_sources > all
> >                all_sources | xargs ....{snip}...
> >
> > This will generate a regular file named `all' in the repository, which
> > is not included in .gitignore.
> > Do we really need this file? I think the second run of all_source is
> > enough.  Or otherwise should
> > we add it into .gitignore?
> >
> > I'm not subscribing linux-kbuild list so please CC me in replies, thanks.
> >
> 
> Besides, there are still some asm-{arch} under include/ now.  The
> current kbuild/scripts will find them by default, which seems not to
> be a good idea:
> 
> 
> $ grep "include/asm-" cscope.files |awk -F"/" '{ print $2 }'|uniq
> asm-generic
> asm-frv
> asm-h8300
> asm-m68k
> asm-mn10300
> asm-m32r
> asm-arm
> asm-xtensa

All architectures are scehuled to move their .h files to
arch/$ARCH/include/* in this merge window.

So when this has happened we are all clear.

	Sam

  reply	other threads:[~2008-12-30  9:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30  6:17 Do we really need file `all'? Jike Song
2008-12-30  7:36 ` Jike Song
2008-12-30  9:24   ` Sam Ravnborg [this message]
2008-12-30  9:28     ` Jike Song
2008-12-30  9:22 ` 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=20081230092401.GB27321@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=albcamus@gmail.com \
    --cc=linux-kbuild@vger.kernel.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