Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262522AbTKNW4W (ORCPT ); Fri, 14 Nov 2003 17:56:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262729AbTKNW4W (ORCPT ); Fri, 14 Nov 2003 17:56:22 -0500 Received: from scrub.xs4all.nl ([194.109.195.176]:25863 "EHLO scrub.xs4all.nl") by vger.kernel.org with ESMTP id S262522AbTKNW4V (ORCPT ); Fri, 14 Nov 2003 17:56:21 -0500 Date: Fri, 14 Nov 2003 23:55:55 +0100 (CET) From: Roman Zippel X-X-Sender: roman@serv To: Geert Uytterhoeven cc: Tupshin Harper , Linux Kernel Mailing List Subject: Re: kernel.bkbits.net off the air In-Reply-To: Message-ID: References: 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: 1229 Lines: 29 Hi, On Fri, 14 Nov 2003, Geert Uytterhoeven wrote: > So if all individual mails were archived somewhere with correct sequence > numbers, they could be used to recreate the whole repository in whatever format > you want. I guess it's just a matter of importing them like patches into arch. The problematic part are "correct sequence numbers" here. These numbers in the commit list mails are pretty much useless. At least the numbers in this line: # ChangeSet 1.1437+1.1350.5.10 -> 1.1438 have to be replaced with a unique identifier. This identifier does exist, e.g. it's visible in the exclude mails. As soon as someone finds out how to export changesets in this format and stores them somewhere, other people can make use of this data. Unfortunately it's rather unlikely that anyone who can do the first, knows also how to do the latter (but maybe Larry can tell us the trick). Anyway, if someone has this data I'd be interested in a copy. 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/