From owner-freebsd-hackers Mon Dec 22 16:51:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA15287 for hackers-outgoing; Mon, 22 Dec 1997 16:51:20 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA15267 for ; Mon, 22 Dec 1997 16:51:12 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id QAA05369; Mon, 22 Dec 1997 16:49:26 -0800 (PST) To: Dmitrij Tejblum cc: Julian Elischer , Luoqi Chen , hackers@freebsd.org Subject: Re: msdosfs win95 long file name support In-reply-to: Your message of "Tue, 23 Dec 1997 03:43:06 +0300." <199712230043.DAA02018@tejblum.dnttm.rssi.ru> Date: Mon, 22 Dec 1997 16:49:26 -0800 Message-ID: <5365.882838166@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > But tracking is easy. Just say 'cvs import ...' and 'cvs update -j ...'... > Btw, NetBSD is not a 'vendor' for other subsystems, but 'vendor' for msdosfs. The technical side is easy. Getting someone to do the work reliably on an ongoing basis, that seems to be the really hard part. :-) > But what if someone enthusiastic about a merge? :) If everyone's agreed on some sort of solution that can: A) Make it into 3.0-current during our current lifetimes. B) Be technically pure and attractive enough that everyone involved doesn't mind working on it. Then sure. Otherwise, what'd be the point? It would simply be another doomed effort. Jordan