Lets make fun of whining democrats thread
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 13
EXTRAVERSION =
NAME=Woozy Numbat
# *DOCUMENTATION*
# 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
# descending is started. They are now explicitly listed as the
# prepare rule.
# To put more focus on warnings, be less verbose as default
# Use 'make V=1' to see the full commands
ifdef V
ifeq ("$(origin V)", "command line")
KBUILD_VERBOSE = $(V)
endif
endif
ifndef KBUILD_VERBOSE
KBUILD_VERBOSE = 0
endif
# Call sparse as part of compilation of C files
# Use 'make C=1' to enable sparse checking
ifdef C
ifeq ("$(origin C)", "command line")
KBUILD_CHECKSRC = $
PATCHLEVEL = 6
SUBLEVEL = 13
EXTRAVERSION =
NAME=Woozy Numbat
# *DOCUMENTATION*
# 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
# descending is started. They are now explicitly listed as the
# prepare rule.
# To put more focus on warnings, be less verbose as default
# Use 'make V=1' to see the full commands
ifdef V
ifeq ("$(origin V)", "command line")
KBUILD_VERBOSE = $(V)
endif
endif
ifndef KBUILD_VERBOSE
KBUILD_VERBOSE = 0
endif
# Call sparse as part of compilation of C files
# Use 'make C=1' to enable sparse checking
ifdef C
ifeq ("$(origin C)", "command line")
KBUILD_CHECKSRC = $
LETTERS
Refusing gift is more than just a technicality
May 4, 2006
Your April 27 editorial, "The iLobby," wrongly suggested that my decision to return a free iPod sent to my office from lobbyists reflected a lack of technological understanding. How sad that The Times would think the only way to get a message to Congress is via expensive gifts. Isn't that what's wrong with Washington? We don't need a digital version of Duke Cunningham.
I am a friend of the technology community because I make good public policy, not because I want a free iPod. I've been named to BusinessWeek's "Digital Dozen" of the top tech-savvy legislators. I've introduced legislation to expand broadband Internet access to more communities. I'll continue to work to implement policies that keep us on the cutting edge. And I'll stick with the iPod my daughter gave me for Christmas two years ago.
SEN. JOHN KERRY
D-Mass.
Refusing gift is more than just a technicality
May 4, 2006
Your April 27 editorial, "The iLobby," wrongly suggested that my decision to return a free iPod sent to my office from lobbyists reflected a lack of technological understanding. How sad that The Times would think the only way to get a message to Congress is via expensive gifts. Isn't that what's wrong with Washington? We don't need a digital version of Duke Cunningham.
I am a friend of the technology community because I make good public policy, not because I want a free iPod. I've been named to BusinessWeek's "Digital Dozen" of the top tech-savvy legislators. I've introduced legislation to expand broadband Internet access to more communities. I'll continue to work to implement policies that keep us on the cutting edge. And I'll stick with the iPod my daughter gave me for Christmas two years ago.
SEN. JOHN KERRY
D-Mass.









