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:from:to:subject:date:message-id:content-type :content-transfer-encoding:mime-version; q=dns; s=default; b=sBj nCxRn2OPwWmr1Fh13gFqJaS/PYTq4cgBP84oZC3wnqclq8C4QXzNeC7suvu7hr0y q9mn+M1P0LJubKUIcAhFB8UlF3n+jtzyUTNiMtrU+uZlKblrQC8yHYgHm4TotQYl wE87Wt1ajgQ8YFg8X6glRqslIdVtsGmVt2EF0Y4U= 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:from:to:subject:date:message-id:content-type :content-transfer-encoding:mime-version; s=default; bh=iQ8vS3CFs jFx1/zB0piCzWoT73c=; b=ETD6AH1UZr1zWT23+LfsTnUNoPL1GmJUrD2M6WZJr sJ7OUEnUPiqwnPM1jQTHOJHzVAMVCkDASeLiM+g2LgD7kOOZjbmgc4RQPPOvrv8p 0+7kY/4qocoX07tDp3x97QiBjpS0CS1FiIKxjQau0BC7SgIjbPXfhzg8d0TYDnBq iw= 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_00,RCVD_IN_HOSTKARMA_NO,RDNS_NONE autolearn=no version=3.3.1 From: "Nellis, Kenneth" To: "cygwin AT cygwin DOT com" Subject: RE: Cygwin and x: directory Date: Fri, 12 Jul 2013 20:09:45 +0000 Message-ID: <0D835E9B9CD07F40A48423F80D3B5A7021D8E0FC@USA7109MB022.na.xerox.net> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id r6CKAIP5032199 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 $ It would seem that touch and rm are following different rules regarding how files may be named. --Ken Nellis -- 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