All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vandrovec <petr@vandrovec.name>
To: David Woodhouse <dwmw2@infradead.org>
Cc: torvalds@osdl.org, akpm@osdl.org, sam@ravnborg.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT *] Remove inclusion of obsolete <linux/config.h>
Date: Wed, 12 Jul 2006 01:35:58 +0200	[thread overview]
Message-ID: <44B435DE.4040708@vandrovec.name> (raw)
In-Reply-To: <1152631729.3373.197.camel@pmac.infradead.org>

David Woodhouse wrote:
> Linus, please pull from git://git.infradead.org/~dwmw2/killconfig.h.git

> Sam thinks it should be a #warning instead, even though it's been
> unnecessary to include config.h for about eight months now. If you
> agree, pull from git://git.infradead.org/~dwmw2/woundconfig.h.git
> instead -- that differs from the first in that it turns config.h into a
> #warning instead.

Well, it is probably unnecessary to include config.h for about eight months, but 
as it is not present in feature-removal-schedule.txt I've missed it.  Thanks for 
pointing it out...

FYI, fortunately (for you, unfortunately for VMware) 2.6.18's already broke our 
build script due to UTS_RELEASE being moved to separate file, so from VMware's 
viewpoint killconfig.h.git will not do any additional damage...

> Please pull one or the other, as you see fit.

								Petr Vandrovec


  reply	other threads:[~2006-07-11 23:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-11 15:28 [GIT *] Remove inclusion of obsolete <linux/config.h> David Woodhouse
2006-07-11 23:35 ` Petr Vandrovec [this message]
2006-07-12  3:37   ` Sam Ravnborg
2006-07-12 11:00     ` Petr Vandrovec
2006-07-12 12:51       ` Arjan van de Ven
2006-07-12 13:54         ` Petr Vandrovec
  -- strict thread matches above, loose matches on Subject: below --
2006-07-06 13:07 David Woodhouse
2006-07-06 13:11 ` David Woodhouse
2006-07-06 17:29   ` Greg KH

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=44B435DE.4040708@vandrovec.name \
    --to=petr@vandrovec.name \
    --cc=akpm@osdl.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.