From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Snook Subject: Re: Versioning file system Date: Tue, 19 Jun 2007 16:10:47 -0400 Message-ID: <46783847.1020205@redhat.com> References: <46731169.2090002@hawkeye.stone.uk.eu.org> <4673182B.4090800@redhat.com> <46739E89.1080003@hawkeye.stone.uk.eu.org> <46781A5B.9090104@redhat.com> <467829C4.5020101@zytor.com> <46782AA5.2000108@hawkeye.stone.uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "H. Peter Anvin" , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, akpm@linux-foundation.org, viro@zeniv.linux.org.uk, alan To: Jack Stone Return-path: Received: from mx1.redhat.com ([66.187.233.31]:53565 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761242AbXFSULH (ORCPT ); Tue, 19 Jun 2007 16:11:07 -0400 In-Reply-To: <46782AA5.2000108@hawkeye.stone.uk.eu.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Jack Stone wrote: > H. Peter Anvin wrote: >> Chris Snook wrote: >>> I pointed out NetApp's .snapshot directories because that's a method >>> that uses legal path character, but doesn't break anything. With this >>> method, userspace tools will have to be taught that : is suddenly a >>> special character. >> Not to mention that the character historically used for this purpose is >> ; (semicolon.) > > But that would cause havoc with shells which use ; to seperate commands. > Using ; would defiantly break userspace > > Jack > I can escape the semicolon just fine in bash. In fact, tab-completion will do this automatically. That's really a non-issue. It just means that anyone who wants to use this feature would have to know what they're doing, which I believe is your goal, right? -- Chris