git pull problems from vim repository

[Charles Campbell]

Hello:

I seem to have a problem doing git pull:

    fatal: Not a git repository (or any parent up to mount point /home)
    Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM
not set).

Fortunately git clone https://github.com/vim/vim.git works, but that's a
lot more work.

Any suggestions on how to fix the git pull?
Chip Campbell

[Gary Johnson]

It worked fine for me just now. Pulled and built without any
issues.

$ git remote -v
origin https://github.com/vim/vim.git (fetch)
origin https://github.com/vim/vim.git (push)

$ git --no-pager log -1 HEAD
commit 94d729cbe8f0f788d9d7539f733cff395e73b228 (HEAD -> master, tag: v8.2.0784, origin/master, origin/HEAD)
Author: Bram Moolenaar <Br...@vim.org>
Date: Sun May 17 21:50:16 2020 +0200

patch 8.2.0784: libvterm code lags behind the upstream version

Problem: Libvterm code lags behind the upstream version.
Solution: Include revisions 730 - 733.

Since git thinks the directory in which you executed "git pull" is
not a git repository, I'd look in that directory and above for the
.git directory. Maybe it got deleted? Maybe you accidentally ran
git in the wrong directory?

HTH,
Gary

[Tony Mechelynck]

This kind of error happens when you aren't in the right repository:
ideally, the current repository should be, not the one which was
current when you cloned the master repo, but the one below that, which
you created by the clone operation and which contains subdirectories
src/ runtime/ etc. and IIUC .git/

I've had the equivalent error on Mercurial in the past. Usually a cd
to the appropriate top-of-the-clone directory fixed it.

If you are absolutely sure that you were in the _immediate_ parent of
src/ runtime/ .git/ etc. then I don't know.

Best regards,
Tony.

[Charles Campbell]

Thanks! -- my script which I run to do the updating (which included git
pull) was, as you surmised, going to the wrong directory. Seems fixed now!
Chip