X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CF2AE3858422 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1684578936; bh=oDDPgI6O25P/f/xpqSB4xJmEjvkV5PZU/H1z3JeNjhk=; h=Date:To:Cc:Subject:References:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=v+K5fxgT3nquMT0BAwMeNlfTmwTeNbXAlqkFPt4IFvj9g72CtRxk7Yf8i0gai1twD QcmRhuX95ujGJKJ0Z2t9NxtK6DJmcs4GwIIWxztbTf2El3GVlbwKy+uqP0Gk/oeesf RZeF2W3ymP0bAdw2Px0MM/AZZJ3/x9llpwwlhCTg= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org EA5913858C52 Date: Sat, 20 May 2023 11:35:17 +0100 To: "Fuchs, Thorsten" Cc: cygwin AT cygwin DOT 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-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 X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Adam Dinwoodie via Cygwin Reply-To: Adam Dinwoodie Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" 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 -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple