Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S292389AbSBYXCf>; Mon, 25 Feb 2002 18:02:35 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S292391AbSBYXC0>; Mon, 25 Feb 2002 18:02:26 -0500
Received: from quechua.inka.de ([212.227.14.2]:30572 "EHLO mail.inka.de")
	by vger.kernel.org with ESMTP id <S292389AbSBYXCQ>;
	Mon, 25 Feb 2002 18:02:16 -0500
From: Bernd Eckenfels <ecki-news2002-02@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18 - Full tarball is OK
In-Reply-To: <200202252149.g1PLnwe13182@directcommunications.net>
X-Newsgroups: ka.lists.linux.kernel
User-Agent: tin/1.5.8-20010221 ("Blue Water") (UNIX) (Linux/2.0.39 (i686))
Message-Id: <E16fU8N-0002FD-00@sites.inka.de>
Date: Tue, 26 Feb 2002 00:02:15 +0100
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

In article <200202252149.g1PLnwe13182@directcommunications.net> you wrote:
> So, I think, it's only patch-2.4.18 that has the problem...

Which is a pretty serious problem. Because ppl using patches hav different
source from ppl using tarball. This will get a lot of confusion for the 2.4.19
patch. I suggest to fix the 2.4.18 patch, even it this is not the best method
to keep unique version numbers.

Greetings
Bernd
-
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/