From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Riesen Subject: Re: [RFC] embedded TAB and LF in pathnames Date: Sat, 8 Oct 2005 01:29:09 +0200 Message-ID: <20051007232909.GB8893@steel.home> References: <7vu0ftyvbc.fsf@assigned-by-dhcp.cox.net> Reply-To: Alex Riesen Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: git@vger.kernel.org, Kai Ruemmler X-From: git-owner@vger.kernel.org Sat Oct 08 01:29:37 2005 Return-path: Received: from vger.kernel.org ([209.132.176.167]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EO1eZ-0005Bv-GR for gcvg-git@gmane.org; Sat, 08 Oct 2005 01:29:27 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964871AbVJGX3X (ORCPT ); Fri, 7 Oct 2005 19:29:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964874AbVJGX3X (ORCPT ); Fri, 7 Oct 2005 19:29:23 -0400 Received: from devrace.com ([198.63.210.113]:40971 "EHLO devrace.com") by vger.kernel.org with ESMTP id S964871AbVJGX3W (ORCPT ); Fri, 7 Oct 2005 19:29:22 -0400 Received: from tigra.home (p54A0E160.dip.t-dialin.net [84.160.225.96]) (authenticated bits=0) by devrace.com (8.12.11/8.12.11) with ESMTP id j97Nfa9i081397; Fri, 7 Oct 2005 18:41:37 -0500 (CDT) (envelope-from fork0@users.sourceforge.net) Received: from steel.home ([192.168.1.2]) by tigra.home with esmtp (Exim 3.36 #1 (Debian)) id 1EO1eH-0006WJ-00; Sat, 08 Oct 2005 01:29:09 +0200 Received: from raa by steel.home with local (Exim 4.42 #1 (Debian)) id 1EO1eH-00027Y-HA; Sat, 08 Oct 2005 01:29:09 +0200 To: Junio C Hamano Content-Disposition: inline In-Reply-To: <7vu0ftyvbc.fsf@assigned-by-dhcp.cox.net> User-Agent: Mutt/1.5.6i X-Spam-Status: No, score=0.4 required=4.5 tests=AWL,BAYES_20, RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL autolearn=no version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on devrace.com Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: Junio C Hamano, Fri, Oct 07, 2005 21:35:19 +0200: > I have not made up my mind on the exact choice of the quoting > convention. We could say '///' instead of '//', for example, or > even '//{LF}//' instead of '//0A' proposed above. One thing I > am trying to avoid is "foo\nbar", which I suspect would be > unfriendly to the Cygwin folks. Being unhappy one of them, I think I'd better manage (even if by postprocessing the output). Please, don't make the common case ugly just because of that platform (insanely broken anyway).