X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=Teb6n9jq6XierkrXx6WEMSbEVOMObVsrcRJKGscu16IO9XTzupFpV 1o/1dpWY/j6OkWQYq2n6dE36e+Ui4RK50btNJT+JXT73gNPj4i+di13ynIfwjVfd NEUuh0EzULyTXXwPE+jwaNZZIxeurtdqZuPNdnlSVyZh6ntS1Ic2X0= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=4ptI0IR/2qBoohCjWt9jHYXqRUg=; b=MEWutDcqjqBvfIBO78XxwNgwl22A 99Uq8N5UK6ZLhru5adrHX/8aUe2Sx4yJAZ4ljabU0PXAmkO0V7svJFtjnxBK0tyY zpwgck3CENWq7J8lN5zTFDeF71riwJvAZaPM47DknZVymk5Cr+mh5nJMRYHl6tQ+ g2tMBZ9Ox9bsUIs= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=-0.1 required=5.0 tests=AWL,BAYES_50,RDNS_NONE autolearn=no version=3.3.1 Date: Mon, 15 Jul 2013 12:40:18 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Cygwin and x: directory Message-ID: <20130715104018.GB18483@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <0D835E9B9CD07F40A48423F80D3B5A7021D8E0FC AT USA7109MB022 DOT na DOT xerox DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A7021D8E0FC@USA7109MB022.na.xerox.net> User-Agent: Mutt/1.5.21 (2010-09-15) On Jul 12 20:09, Nellis, Kenneth wrote: > On 07/12/2013 08:42 AM, Mikko Rapeli wrote: > > > > Hi Cygwin and git developers, > > > > Does following scenario show signs of bugs in Cygwin and/or git? > > > > # setup git repo > > $ cd /tmp > > $ mkdir foo && cd foo > > $ git init > > > > # create x: directory > > $ mkdir x: > > $ ls > > x: > > IMHO, this makes an interesting problem (unrelated to git): > Shell script prompts user for file name. > User enters "x:". > Script proceeds as follows: > $ mkdir tmpdir > $ touch tmpdir/x: > $ # useful work done here > $ rm -r tmpdir > rm: cannot remove `tmpdir/x:': No such file or directory > rm: cannot remove `tmpdir': Directory not empty > $ That's a problem of how recursive rm works. It chdir's into the subdirs it's working on and then calls "x:" which is recognized as drive prefix of a windows path. `rm ./x:' works as expected. > It would seem that touch and rm are following different > rules regarding how files may be named. No. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple