From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lucy.dinwoodie.org (lucy.dinwoodie.org [IPv6:2001:8b0:de15:20ad:6beb:fd8f:c6fd:d1ac]) by sourceware.org (Postfix) with ESMTPS id EA5913858C52 for ; Sat, 20 May 2023 10:35:19 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org EA5913858C52 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=dinwoodie.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=dinwoodie.org Received: from adam by lucy.dinwoodie.org with local (Exim 4.96) (envelope-from ) id 1q0Jvh-002W4F-1g; Sat, 20 May 2023 11:35:17 +0100 Date: Sat, 20 May 2023 11:35:17 +0100 From: Adam Dinwoodie To: "Fuchs, Thorsten" Cc: cygwin@cygwin.com Subject: Re: git 2.39.0 change from relative to absolute submodule paths Message-ID: <20230520103517.4chppsq67z4ivjjm@lucy.dinwoodie.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,KAM_DMARC_STATUS,SPF_HELO_PASS,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Wed, May 17, 2023 at 06:26:38AM +0000, Fuchs, Thorsten via Cygwin wrote: > Hello, > > After submodule update with git 2.39.0 some of our sub modules got > their worktree settings in the .git/modules//config fil set > as absolute paths. See the attached config files as example. It seems > that if the path is changed from relative. Not all submodules are > effected. It happens also sporadically and not and very frequently. > > It is possible to carry on working Cygwin git. However, we are using > Tortoise git with libgit2 and git for windows in parallel. Due to the > absolute Cygwin paths this is not working anymore. > > We have not yet seen such a behavior in git for windows. Also we can't > reproduce it at this point in time. We consider it a bug but nor sure > about it. This is odd. I suspect rewriting the paths like this is something in the upstream Git project, rather than anything Cygwin-specific (although clearly the issues it's causing are Cygwin-specific). I don't think there's enough information here for me to investigate or report upstream, unfortunately; what I really need is information about what triggers the behaviour so I can reproduce the problem. If you manage to work out how to reproduce this behaviour, rather than just noticing it after the fact, that would be incredibly useful and I can take things from there. Adam