|author||Adrian Bunk <firstname.lastname@example.org>||2008-01-27 16:58:41 (GMT)|
|committer||Adrian Bunk <email@example.com>||2008-01-27 16:58:41 (GMT)|
|commit||ae793603c3a69cf676d48233106e515fbdf4ceb2 (patch) (side-by-side diff)|
1 files changed, 1 insertions, 1 deletions
@@ -1,28 +1,28 @@
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 16
-EXTRAVERSION = .60-rc1
+EXTRAVERSION = .60
# To see a list of typical targets execute "make help"
# More info can be located in ./README
# Comments in this file are targeted only to the developer, do not
# expect to learn how to build the kernel reading this file.
# Do not print "Entering directory ..."
MAKEFLAGS += --no-print-directory
# We are using a recursive build, so we need to do a little thinking
# to get the ordering right.
# Most importantly: sub-Makefiles should only ever modify files in
# their own directory. If in some directory we have a dependency on
# a file in another dir (which doesn't happen often, but it's often
# unavoidable when linking the built-in.o targets which finally
# turn into vmlinux), we will call a sub make in that other dir, and
# after that we are sure that everything which is in that other dir
# is now up to date.
# The only cases where we need to modify files which have global
# effects are thus separated out and done before the recursive