linux.git/scripts/kconfig/util.c, branch v2.6.16 Linux kernel source tree Merge git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild 2006-01-05T00:36:52+00:00 Linus Torvalds torvalds@g5.osdl.org 2006-01-05T00:36:52+00:00 25c862cc9ea9b312c25a9f577f91b973131f1261 






s/retreiv/retriev/g
2006-01-03T12:27:11+00:00

Matt Mackall
mpm@selenic.com

2006-01-03T12:27:11+00:00

4a4efbdee278b2f4ed91aad2db5c006ff754276e

As everyone knows, the rule is: "i before e.. um.. always."

Signed-off-by: Matt Mackall <mpm@selenic.com>
Signed-off-by: Adrian Bunk <bunk@stusta.de>





As everyone knows, the rule is: "i before e.. um.. always."

Signed-off-by: Matt Mackall <mpm@selenic.com>
Signed-off-by: Adrian Bunk <bunk@stusta.de>







kbuild: always run 'make silentoldconfig' when tree is cleaned
2005-12-26T22:34:03+00:00

Sam Ravnborg
sam@mars.ravnborg.org

2005-12-26T22:34:03+00:00

752625cff3eba81cbc886988d5b420064c033948

If the file .kconfig.d is missing then make sure to run
'make silentoldconfig', since we have no way to detect if
a Kconfig file has been updated.

-kconfig.d is created by kconfig and is removed as part
of 'make clean' so the situation is likely to occur in reality.

Jan Beulich <JBeulich@novell.com> reported this bug.

Signed-off-by: Sam Ravnborg <sam@ravnborg.org>





If the file .kconfig.d is missing then make sure to run
'make silentoldconfig', since we have no way to detect if
a Kconfig file has been updated.

-kconfig.d is created by kconfig and is removed as part
of 'make clean' so the situation is likely to occur in reality.

Jan Beulich <JBeulich@novell.com> reported this bug.

Signed-off-by: Sam Ravnborg <sam@ravnborg.org>







Linux-2.6.12-rc2
2005-04-16T22:20:36+00:00

Linus Torvalds
torvalds@ppc970.osdl.org

2005-04-16T22:20:36+00:00

1da177e4c3f41524e886b7f1b8a0c1fc7321cac2

Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!





Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!