Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262085AbVBJJx5 (ORCPT ); Thu, 10 Feb 2005 04:53:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262089AbVBJJx5 (ORCPT ); Thu, 10 Feb 2005 04:53:57 -0500 Received: from scrub.xs4all.nl ([194.109.195.176]:6536 "EHLO scrub.xs4all.nl") by vger.kernel.org with ESMTP id S262087AbVBJJwm (ORCPT ); Thu, 10 Feb 2005 04:52:42 -0500 Date: Thu, 10 Feb 2005 10:52:19 +0100 (CET) From: Roman Zippel X-X-Sender: roman@scrub.home To: Larry McVoy cc: Nicolas Pitre , Jon Smirl , tytso@mit.edu, Stelian Pop , Francois Romieu , lkml Subject: Re: [RFC] Linux Kernel Subversion Howto In-Reply-To: <20050210005041.GA26312@bitmover.com> Message-ID: References: <20050209184629.GR22893@bitmover.com> <20050209235312.GA25351@bitmover.com> <20050210005041.GA26312@bitmover.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1005 Lines: 23 Hi, On Wed, 9 Feb 2005, Larry McVoy wrote: > This problem is nowhere near as hard as you are making it out to be > but it is hard. But it's not that bad, we do this every time we do > a CVS import, we have to intuit the changeset boundaries themselves, > which is actually harder than what you are trying to do. Think about > taking revision history without any changeset grouping and recreating > the changesets (aka patches). We do that all the time, automatically. > If we can do that then you can do this. That's simply not true and you know that. I repeat, the bkweb information is not enough to recreate the history, incomplete data will only produce incomplete results no matter how hard you try and I delivered the _proof_ for that. bye, Roman - 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/