From: Adam Dinwoodie <adam@dinwoodie.org>
To: "Fuchs, Thorsten" <Thorsten.Fuchs@brose.com>
Cc: cygwin@cygwin.com
Subject: Re: git 2.39.0 change from relative to absolute submodule paths
Date: Sat, 20 May 2023 11:35:17 +0100 [thread overview]
Message-ID: <20230520103517.4chppsq67z4ivjjm@lucy.dinwoodie.org> (raw)
In-Reply-To: <DB8PR08MB4011551CD0987865BF92D0F7947E9@DB8PR08MB4011.eurprd08.prod.outlook.com>
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/<submodul>/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
next prev parent reply other threads:[~2023-05-20 10:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 6:26 Fuchs, Thorsten
2023-05-20 10:35 ` Adam Dinwoodie [this message]
2023-05-21 16:07 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230520103517.4chppsq67z4ivjjm@lucy.dinwoodie.org \
--to=adam@dinwoodie.org \
--cc=Thorsten.Fuchs@brose.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).