From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32784 invoked by alias); 4 Dec 2015 17:04:50 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 32776 invoked by uid 89); 4 Dec 2015 17:04:50 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-wm0-f42.google.com Received: from mail-wm0-f42.google.com (HELO mail-wm0-f42.google.com) (74.125.82.42) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Fri, 04 Dec 2015 17:04:48 +0000 Received: by wmvv187 with SMTP id v187so83832090wmv.1 for ; Fri, 04 Dec 2015 09:04:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=dZRuqx855DwQz00nVAUstGx1H5clk57Nwd2REbtQzsU=; b=dhITcMRgHhB7a9TnJ7ZGeoqM+Y2NQa/rHX+Z6rp2wTHQFqZOCBwGhqGSI9PvTTjXS8 9Nx+Z40AWD2cut0Zf51g0imc8DooXfQl1qBEi2CY9SgT5QNwNRBP+2t16HzVRthfah+o IQTndopv1GCfGPL9iaDkkbkFMgj2aJDx63qW2VoClyohY0+ysVVQVjfYkShc6NahhSRv 4ALbwMLBszr76j51V8kkbnZn8eRznjWJ6PMHuXtC10kbGMXInAwn0lbrPdv+2MqLSA4i xvMEbsRYX6nCEU4poBsPshLABHBi7XZBCOHE8tj8hOf7W3XgZFhp+tptHGA0ya3XqxZr XLlw== X-Gm-Message-State: ALoCoQmWMKX/dNFyhz2KsX48hl8g2VSDZPHAXdyXCcsxS/VmPyd10wnwdS4q6eP1/ECVZ6QjlU+Z X-Received: by 10.28.65.69 with SMTP id o66mr5986691wma.18.1449248685152; Fri, 04 Dec 2015 09:04:45 -0800 (PST) Received: from dinwoodie.org ([2001:ba8:0:1c0::9:1]) by smtp.gmail.com with ESMTPSA id kj3sm12896018wjb.19.2015.12.04.09.04.44 for (version=TLS1_2 cipher=AES128-SHA bits=128/128); Fri, 04 Dec 2015 09:04:44 -0800 (PST) Date: Fri, 04 Dec 2015 17:04:00 -0000 From: Adam Dinwoodie To: cygwin@cygwin.com Subject: Re: Git issue. Message-ID: <20151204170442.GL14466@dinwoodie.org> References: <1032375163.9174650.1448234447549.JavaMail.zimbra@comcast.net> <1271139068.9180259.1448235027708.JavaMail.zimbra@comcast.net> <20151203204221.GK14466@dinwoodie.org> <45790306.1954012.1449187639543.JavaMail.zimbra@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45790306.1954012.1449187639543.JavaMail.zimbra@comcast.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes X-SW-Source: 2015-12/txt/msg00047.txt.bz2 On Fri, Dec 04, 2015 at 12:07:19AM +0000, Matt Smith wrote: > > On Sun, Nov 22, 2015 at 11:30:27PM +0000, boulderfans wrote: > > > [/cygdrive/d/projects] > > > $ git --git-dir=d:/projects/git-git/.git config alias.foo ls-files > > > error: Unable to open tempfile: /cygdrive/d/projects/d:/projects/git-git/.git/config.lock > > > error: could not lock config file d:/projects/git-git/.git/config: No such file or directory > > > > > > The problem is that the code that is checking the --git-dir option > > > doesn't work properly if you use a DOS drive:/path specification. > > > > Cygwin applications, including applications you've compiled yourself > > using the Cygwin toolchain, normally expect Cygwin's Linux-like paths, > > e.g. /cygdrive/d/projects/git-git. Attempting to use Windows paths > > simply isn't meant to work. > > > > You can convert from a Windows path to the equivalent Cygwin path using > > the cygpath utility, e.g.: > > > > git --git-dir="$(cygpath 'd:/projects/git-git/.git')" config alias.foo ls-files > > Ok. I wasn't sure as the behavior changed. It worked in 1.9.5 and > then stopped working when I moved to 2.5.x. I'm not sure if it > matters to you, but doing some bisecting it looks like the behavior > changed between 2.2.0 and 2.3.0: Please don't top post on this list, and please don't quote raw email addresses. See https://cygwin.com/acronyms/#TOFU for a brief note on the whys. Out of curiosity, I wrote a short bisect script to test this behaviour; the behaviour changed in v2.2.0-rc0-1-gfa137f6, which changed handling of lock files; it looks like it broke your scenario as a side-effect. However, as I say, this isn't something that was ever supposed to work; that it did in the past was coincidence rather than design, so I don't think you'll have any luck getting the old behaviour back. Using cygpath to convert between Windows and Cygwin paths, and otherwise sticking to Linux/Cygwin-style paths for Cygwin applications and Windows paths for Windows ones, is the correct way to go about this. -- 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