From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pat LaVarre Subject: editable udf metadata Date: 26 Nov 2003 08:58:48 -0700 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <1069862328.4325.30.camel@patrh9> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from email-out1.iomega.com ([147.178.1.82]:33196 "EHLO email.iomega.com") by vger.kernel.org with ESMTP id S264239AbTKZP7V (ORCPT ); Wed, 26 Nov 2003 10:59:21 -0500 Received: from royntex01.iomegacorp.com (unknown [147.178.90.120]) by email.iomega.com (Postfix) with ESMTP id EEC462473 for ; Wed, 26 Nov 2003 08:59:20 -0700 (MST) To: linux-fsdevel@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Kindly offline I was asked to summarise & elaborate: 1) The udfct udf_test (aka the Philips UDF Verifier) encourages you to fetch udftools via cvs rather than via http of sourceforge, per such procedures as: http://marc.theaimsgroup.com/?l=linux-fsdevel&m=106692617907993 List: linux-fsdevel Subject: Re: editable udf metadata Date: 2003-10-23 16:06:26 2) The cvs udftools you get that way didn't change between 2003-10-24 and 2003-11-26. 3) A snapshot of the cvs udftools, by design likely to fall behind just as http sourceforge does, appears at: ftp://members.aol.com/plscsi/linux/ 4) When fetching via plscsi/ you can say http rather than ftp if you like: http://members.aol.com/plscsi/linux/ Pat LaVarre