public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: Git unable to construct submodule's relative path
Date: Fri, 28 Jun 2019 11:22:00 -0000	[thread overview]
Message-ID: <CA+kUOan1cq4rNcmj=0q92zfcLpMo0hTchODa1V-32VO8D6nDsg@mail.gmail.com> (raw)
In-Reply-To: <517680510.20190626195940@yandex.ru>

On Wed, 26 Jun 2019 at 18:05, Andrey Repin wrote:
> Checking out the https://gitlab.com/norganna-wow/all I've noticed a problem in
> updating submodules after first init.
> Inspecting the Git config area, I stumbled upon paths like
>
> worktree = ../../../../../../../../../anrdaemon/Documents/Games/WoW/NorgannaAddons/auctioneer/Auc-Advanced
>
> which is obviously wrong.
> To begin with, there's not enough parent directories to fill the path, and
> even if I correct the path to
>
> worktree = ../../../../auctioneer/Auc-Advanced
>
> the next run of "git submodule update --recursive --remote" trashes it again.

Works just fine for me.

Can you please explain, step-by-step, exactly what you're doing, what
commands you're running, what you're seeing, and how that differs from
what you expect to see?

For future reference, there's a good guide to providing useful
bug/problem reports at
https://www.chiark.greenend.org.uk/~sgtatham/bugs.html, which is
linked from the Cygwin problem reporting guidance page at
http://cygwin.com/problems.html.

--
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

      reply	other threads:[~2019-06-28 11:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-26 17:05 Andrey Repin
2019-06-28 11:22 ` Adam Dinwoodie [this message]

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='CA+kUOan1cq4rNcmj=0q92zfcLpMo0hTchODa1V-32VO8D6nDsg@mail.gmail.com' \
    --to=adam@dinwoodie.org \
    --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).