From: Sverre Rabbelier <srabbelier@gmail.com>
Date: Mon, 16 Feb 2009 14:40:11 GMT
Subject: Re: [RFC - draft] List of proposed future changes that are backward incompatible
Message-ID: <bd6139dc0902160640n3a95223j71ae7f26bc0ff0b4@mail.gmail.com>
In-Reply-To: <alpine.DEB.1.10.0902160731420.14911@asgard.lang.hm>

On Mon, Feb 16, 2009 at 16:33,  <david@lang.hm> wrote:
> if it is the correct thing to do with some workloads, it's not being
> deprecated. if it was deprecated then it is a capability that would be
> scheduled for complete removal, and nobody should ever use. not just the
> case where it needs to be used carefully, and you are putting in a warning
> about it.

Nitpicking much? The reasons why the warning/default-to-disallow are
being put in place have been explained, what value did your message
above add to the discussion? From my point of view it didn't add much,
if anything at all. It might be a good idea to end this thread here,
as Junio requested. If you feel the undying need to continue this
discussion, please do not do so in this thread.

Thank you.

-- 
Cheers,

Sverre Rabbelier