From: Andrew Morton <akpm@osdl.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: zippel@linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 11/19] kconfig: move .kernelrelease
Date: Mon, 10 Apr 2006 02:58:51 -0700 [thread overview]
Message-ID: <20060410025851.641022a0.akpm@osdl.org> (raw)
In-Reply-To: <20060410104250.GA24160@mars.ravnborg.org>
Sam Ravnborg <sam@ravnborg.org> wrote:
>
> On Mon, Apr 10, 2006 at 01:57:27AM -0700, Andrew Morton wrote:
> > Roman Zippel <zippel@linux-m68k.org> wrote:
> > >
> > > This moves the .kernelrelease file into include/config directory.
> > > Remove its generation from the config step, if the config step doesn't
> > > leave a proper .config behind, it triggers a call to silentoldconfig.
> > > Instead its generation can be done via proper dependencies.
> >
> > Well that was a pita. I was using that file in my kernel installation
> > script.
> >
> > Your changelog says what the patch does, but gives no indication of why it
> > did it.
> >
> > What do we get back for the breakage which this will cause?
> >
> > Now I'm going to have to look for both .kernelrelease and
> > include/config/kernel.release and work out which one has the more recent
> > mtime. grr.
> That you have for not using 'make kernelrelease' - he ;-)
> Did you not know, or did make kernelrelease not do what you expected?
>
I stopped using `make kernelrelease' when it did something bad when used
from another machine across NFS.
<tries it>
hm, it takes nearly five seconds, but it wasn't that - something actually
broke. But I forget what it was. I'll put it back and will wait for it
to reoccur.
next prev parent reply other threads:[~2006-04-10 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 15:29 Roman Zippel
2006-04-10 8:57 ` Andrew Morton
2006-04-10 10:42 ` Sam Ravnborg
2006-04-10 9:58 ` Andrew Morton [this message]
2006-04-10 10:10 ` Andrew Morton
2006-04-10 13:29 ` Roman Zippel
2006-04-10 20:02 ` Andrew Morton
2006-04-12 13:23 ` Roman Zippel
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=20060410025851.641022a0.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®