DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=XJS9fO4kyagOSs43kFxnCuH0T/mRoOyZJhuOFyuQVlTdjqE6fmWJFbLI49YCBWlEICuh2lHFuC39Od0DesMoQAaUfDZjacBp25eootNPKE/tYv42hNm27yx8pYU6RkXYJIKdHPSwO5ncxdC124RM0YIAfekPUx/cskOJF2I498k=
Message-ID: <35fb2e590504061622364f72a@mail.gmail.com>
Date: Thu, 7 Apr 2005 00:22:30 +0100
From: Jon Masters <jonmasters@gmail.com>
Reply-To: jonathan@jonmasters.org
To: Linus Torvalds <torvalds@osdl.org>
Subject: Re: Kernel SCM saga..
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
In-Reply-To: <Pine.LNX.4.58.0504060800280.2215@ppc970.osdl.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
References: <Pine.LNX.4.58.0504060800280.2215@ppc970.osdl.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 869
Lines: 22

On Apr 6, 2005 4:42 PM, Linus Torvalds <torvalds@osdl.org> wrote:

> as a number of people are already aware (and in some
> cases have been aware over the last several weeks), we've
> been trying to work out a conflict over BK usage over the last
> month or two (and it feels like longer ;). That hasn't been
> working out, and as a result, the kernel team is looking at
> alternatives.

What about the 64K changeset limitation in current releases?

Did I miss something (like the fixes promised) or is there going to be
another interim release before the end of support?

Jon.

P.S. Apologies if this already got addressed.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/