【git】fatal: in unpopulated submodule

最新推荐文章于 2025-04-10 00:03:53 发布
最新推荐文章于 2025-04-10 00:03:53 发布
阅读量2.2k 收藏 6
点赞数 3
分类专栏： linux菜鸟手记 文章标签： git
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/commshare/article/details/120305346
版权

  • 为了直接编译go代码，把依赖库放common下了。
  • 然后， 把下载回来的git 代码上传了
  • 在这里插入图片描述
  • 怎么才能 直接上传代码呢？

直接add报错：fatal: in unpopulated submodule ‘common/atomic’


zhangbin@LAPTOP-F1POBCSR MINGW64 /d/Code/GaoKeYong/RPC/livecdn/common/atomic (master)
$ git add .
fatal: in unpopulated submodule 'common/atomic'

解决：先删掉 git rm --cached . -rf

zhangbin@LAPTOP-F1POBCSR MINGW64 /d/Code/GaoKeYong/RPC/livecdn/common/atomic (master)
$ git rm --cached . -rf
rm 'common/atomic'

然后添加:git add .

zhangbin@LAPTOP-F1POBCSR MINGW64 /d/Code/GaoKeYong/RPC/livecdn/common/atomic (master)
$ git add .
warning: LF will be replaced by CRLF in common/atomic/origin.git/HEAD.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/config.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/description.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/hooks/applypatch-msg.sample.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/hooks/commit-msg.sample.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/hooks/fsmonitor-watchman.sample.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/hooks/post-update.sample.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/hooks/pre-applypatch.sample.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/hooks/pre-commit.sample.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/hooks/pre-merge-commit.sample.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/hooks/pre-push.sample.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/hooks/pre-rebase.sample.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/hooks/pre-receive.sample.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/hooks/prepare-commit-msg.sample.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/hooks/push-to-checkout.sample.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/hooks/update.sample.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/info/exclude.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/logs/HEAD.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/logs/refs/remotes/origin/HEAD.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/packed-refs.
The file will have its original line endings in your working directory
warning: LF will be replaced by CRLF in common/atomic/origin.git/refs/remotes/origin/HEAD.
The file will have its original line endings in your working directory

zhangbin@LAPTOP-F1POBCSR MINGW64 /d/Code/GaoKeYong/RPC/livecdn/common/atomic (master)
$ git commit -m "common atomic"
[master daa9ef9] common atomic
 78 files changed, 4623 insertions(+), 1 deletion(-)
 delete mode 160000 common/atomic
 create mode 100644 common/atomic/.codecov.yml
 create mode 100644 common/atomic/.gitignore
 create mode 100644 common/atomic/CHANGELOG.md
 create mode 100644 common/atomic/LICENSE.txt
 create mode 100644 common/atomic/Makefile
 create mode 100644 common/atomic/README.md
 create mode 100644 common/atomic/assert_test.go
 create mode 100644 common/atomic/bool.go
 create mode 100644 common/atomic/bool_ext.go
 create mode 100644 common/atomic/bool_test.go
 create mode 100644 common/atomic/doc.go
 create mode 100644 common/atomic/duration.go
 create mode 100644 common/atomic/duration_ext.go
 create mode 100644 common/atomic/duration_test.go
 create mode 100644 common/atomic/error.go
 create mode 100644 common/atomic/error_ext.go
 create mode 100644 common/atomic/error_test.go
 create mode 100644 common/atomic/example_test.go
 create mode 100644 common/atomic/float64.go
 create mode 100644 common/atomic/float64_ext.go
 create mode 100644 common/atomic/float64_test.go
 create mode 100644 common/atomic/gen.go
 create mode 100644 common/atomic/go.mod
 create mode 100644 common/atomic/go.sum
 create mode 100644 common/atomic/int32.go
 create mode 100644 common/atomic/int32_test.go
 create mode 100644 common/atomic/int64.go
 create mode 100644 common/atomic/int64_test.go
 create mode 100644 common/atomic/internal/gen-atomicint/main.go
 create mode 100644 common/atomic/internal/gen-atomicwrapper/main.go
 create mode 100644 common/atomic/nocmp.go
 create mode 100644 common/atomic/nocmp_test.go
 create mode 100644 common/atomic/origin.git/HEAD
 create mode 100644 common/atomic/origin.git/config
 create mode 100644 common/atomic/origin.git/description
 create mode 100644 common/atomic/origin.git/hooks/applypatch-msg.sample
 create mode 100644 common/atomic/origin.git/hooks/commit-msg.sample
 create mode 100644 common/atomic/origin.git/hooks/fsmonitor-watchman.sample
 create mode 100644 common/atomic/origin.git/hooks/post-update.sample
 create mode 100644 common/atomic/origin.git/hooks/pre-applypatch.sample
 create mode 100644 common/atomic/origin.git/hooks/pre-commit.sample
 create mode 100644 common/atomic/origin.git/hooks/pre-merge-commit.sample
 create mode 100644 common/atomic/origin.git/hooks/pre-push.sample
 create mode 100644 common/atomic/origin.git/hooks/pre-rebase.sample
 create mode 100644 common/atomic/origin.git/hooks/pre-receive.sample
 create mode 100644 common/atomic/origin.git/hooks/prepare-commit-msg.sample
 create mode 100644 common/atomic/origin.git/hooks/push-to-checkout.sample
 create mode 100644 common/atomic/origin.git/hooks/update.sample
 create mode 100644 common/atomic/origin.git/index
 create mode 100644 common/atomic/origin.git/info/exclude
 create mode 100644 common/atomic/origin.git/logs/HEAD
 create mode 100644 common/atomic/origin.git/logs/refs/remotes/origin/HEAD
 create mode 100644 common/atomic/origin.git/objects/pack/pack-e305082472f87d5ad325142e07ec08ac8bf53d02.idx
 create mode 100644 common/atomic/origin.git/objects/pack/pack-e305082472f87d5ad325142e07ec08ac8bf53d02.pack
 create mode 100644 common/atomic/origin.git/packed-refs
 create mode 100644 common/atomic/origin.git/refs/remotes/origin/HEAD
 create mode 100644 common/atomic/stress_test.go
 create mode 100644 common/atomic/string.go
 create mode 100644 common/atomic/string_ext.go
 create mode 100644 common/atomic/string_test.go
 create mode 100644 common/atomic/time.go
 create mode 100644 common/atomic/time_ext.go
 create mode 100644 common/atomic/time_test.go
 create mode 100644 common/atomic/tools/go.mod
 create mode 100644 common/atomic/tools/go.sum
 create mode 100644 common/atomic/tools/tools.go
 create mode 100644 common/atomic/uint32.go
 create mode 100644 common/atomic/uint32_test.go
 create mode 100644 common/atomic/uint64.go
 create mode 100644 common/atomic/uint64_test.go
 create mode 100644 common/atomic/uintptr.go
 create mode 100644 common/atomic/uintptr_test.go
 create mode 100644 common/atomic/unsafe_pointer.go
 create mode 100644 common/atomic/unsafe_pointer_test.go
 create mode 100644 common/atomic/value.go
 create mode 100644 common/atomic/value_test.go
 create mode 100644 core/agent/registry/service.go

zhangbin@LAPTOP-F1POBCSR MINGW64 /d/Code/GaoKeYong/RPC/livecdn/common/atomic (master)
$ git push origin master
Enumerating objects: 103, done.
Counting objects: 100% (103/103), done.
Delta compression using up to 8 threads
Compressing objects: 100% (85/85), done.
Writing objects: 100% (99/99), 208.94 KiB | 7.74 MiB/s, done.
Total 99 (delta 38), reused 0 (delta 0), pack-reused 0
remote: Powered by GITEE.COM [GNK-6.1]
To gitee.com:ixiaomo/test_-livecdn_-zbtt.git
   87ef9e0..daa9ef9  master -> master

zhangbin@LAPTOP-F1POBCSR MINGW64 /d/Code/GaoKeYong/RPC/livecdn/common/atomic (master)
$
【Git/Bugfix系列】fatal: in unpopulated submodule的分析和解决方案
CSDN明星博主，认证博客专家，视频、Matlab领域优质创作者。
11-28 2166
DATA: 2021.11.26 文章目录1、参考 1、参考 git学习 - git add出现 "in unpopulated submodule ‘A’ " 问题 fatal: in unpopulated submodule git add出现 “fatal: in unpopulated submodule XXX” 错误
【基础】Git
qq_48687155的博客
08-22 489
Git基础
git add出现 “fatal: in unpopulated submodule XXX“ 错误
大洋
01-16 449
因为element_yf_front是从另一个第三方的仓库克隆的，在执行git add的时候"fatal: in unpopulated submodule element_yf_front" 错误。
git报错fatal: unsafe repository
最新发布
长风破浪会有时的博客
04-10 192
从这个版本开始，Git 会检查仓库目录的所有权，如果仓库目录的所有者与当前运行 Git 命令的用户不一致，就会认为该仓库是“不安全的”，从而拒绝执行操作。如果你在多个仓库中遇到类似的问题，需要为每个仓库都执行一次上述命令，将它们添加到安全目录列表中。不过，这样做会降低 Git 的安全性，因为它会允许在任何目录下执行 Git 操作，而不进行所有权检查。因此，建议只在你信任的环境中使用这种方法。这条命令会在全局的 Git 配置文件中添加一个安全目录的条目，允许你在。目录下正常使用 Git 命令。
解决报错：fatal: in unpopulated submodule *
liuzhen007的专栏
11-29 2803
今天想把两个 Git 工程合并成一个工程，尽管已经将其中一个工程的 .git 目录删除了，但是在合并提交时还是遇到了一个和子模块相关的报错，具体报错信息如下： fatal: in unpopulated submodule '*'
fatal: in unpopulated submodule 'xxxxx'
Areigninhell的博客
06-24 2485
原因是原有文件中的.git文件未删除 我出现这个问题是因为在 当前目录（以下写：./）下建立了一个仓库：A 而 ./ 下有一文件夹 命名为“A”，A/ 有之前建立的仓库，我在 ./ 下add commit push 后发现远程仓库内并没有A/的内容，于是我在 A/ 下执行 ”git add .” 提示：“in unpopulated submodule ‘A’ ”（翻译为”在一个无人居住的子模...
git 无法提交某文件 fatal: in unpopulated submodule
luolai的专栏
05-17 357
但是提交到自己建的私有库时，前端文件的项目无法提交，如下图（因为我是把 前端项目的文件统一放在了 后端项目结构中）2、清楚原先 .git的记录 否则 git add 文件夹 会如题错误。也可以idea处理 add 之后 在 commit -> push。（仔细观察 目前所在的目录路径 否则 清楚缓存还是会报错）jeecgboot中 想提交保存下修改的项目工程代码。1、 原先下载的代码，有其原先的.git记录，请删除。重新 git add 文件夹。进入到正确目录路径所在处。
【Hexo异常】fatal: in unpopulated submodule '.deploy_git'
nomasp
03-10 8917
今天又重新搞了下hexo，好久不动它居然报了错。 这种情况可以先安装下相关的依赖： npm install hexo-deployer-git –save 实在不行，就把它删掉，然后重新生成和部署。 rm -rf .deploy_git hexo g hexo d 大功告成！...
D:\git\ci_backend_service\CI_Autoservice\public_library>git add . fatal: in unpopulated submodule 'CI_Autoservice/public_library'
06-14
你可以尝试运行以下命令来初始化 submodule： ``` git submodule update --init --recursive ``` 如果 submodule 已经被初始化，但是你还是遇到了这个错误，那么可能是 submodule 中的某些文件被删除了，你可以...
D:\git\ci_backend_service\CI_Autoservice\public_library>git add .gitmodules fatal: in unpopulated submodule 'CI_Autoservice/public_library' D:\git\ci_backend_service\CI_Autoservice\public_library>
06-14
根据你提供的错误信息，看起来你正在 `public_library` 子模块目录下执行 `git add .gitmodules` 命令，但是子模块尚未被初始化，因此出现了 "in unpopulated submodule" 的错误。 如果你想为子模块添加或修改 `....
D:\git\ci_backend_service\CI_Autoservice\public_library>git add . fatal: in unpopulated submodule 'CI_Autoservice/public_library' D:\git\ci_backend_service\CI_Autoservice\public_library>git submodule update --init --recursive fatal: No url found for submodule path './' in .gitmodules D:\git\ci_backend_service\CI_Autoservice\public_library>
06-14
然后再次尝试运行 `git submodule update --init --recursive` 命令来初始化子模块。如果你有多个子模块，你需要为每个子模块设置 url。 一旦子模块被初始化，你就应该能够成功地运行 `git add .` 命令。
git学习 - git add出现 "in unpopulated submodule 'A' " 问题
guo_lei_lamant的博客
02-05 7886
我出现这个问题是因为在 当前目录（以下写：./）下建立了一个仓库：A 而 ./ 下有一文件夹 命名为“A”，A/ 有之前建立的仓库，我在 ./ 下add commit push 后发现远程仓库内并没有A/的内容，于是我在 A/ 下执行 ”git add .” 提示：“in unpopulated submodule ‘A’ ”（翻译为”在一个无人居住的子模块“，感觉意思是说位于子模块下，无法 ...
git add出现 "fatal: in unpopulated submodule XXX" 错误
热门推荐
青山师
01-29 1万+
git add出现 “fatal: in unpopulated submodule XXX” 错误： 当前处于： F:\217my_optLogs\001系统相关\系统设计\007\oschina\ydgw2407.github.io\themes 下面有目录2个： hexo-theme-matery landscape 因为hexo-theme-matery是从另一个第三方的仓库克隆的，在...
Git学习整理【fatal: in unpopulated submodule 'XXX'】
SunnyCat
04-20 1166
踩坑小记，Git上传到远程库的时候发现一个文件夹上传不成功，报错如下 fatal: in unpopulated submodule 'spider' 原因是这个文件夹来自的库是第三方库，通常这种情况就会出现报错 解决办法： $ git rm -rf --cached spider/ $ git add spider/ $ git commit -m"second add spider" ...
git提交时报:Fatal: unpopulated submodule
qq_40938788的博客
01-29 619
因为我的一个文件是从另外一个仓库里面copy过来的，所以提交的没有提交上去，只是有一个空文件，并且提交还会报错，提示：Fatal: unpopulated submodule 这个时候我们需要去仓库里面去创建文件夹，然后再去提交 例如： ...
Git在添加目录时遇到了Fatal: unpopulated submodule的解决办法
赵星汉同学的博客
06-30 2451
Git在添加目录时遇到了Fatal: unpopulated submodule的解决办法 今天，在把以前的一个目录整体拷贝到git的目录下时，在add的时候遇到了报错，提示unpopulated submodule的信息，无法添加。后来经过查证，可以采用如下的方法解决. 针对提示的目录papers git rm -rf --cached Papers git add Papers/* 问题完美解决。 ...
git fatal: Path '' is in submodule '' 错误
tempsitegoogle
05-24 445
git提交代码是出现fatal: Path 'directory/file' is in submodule 'directory''错误。悲催啊，怎么也没找到，后来把说出错的文件夹（directory）删除了。再提交就OK了。哈哈。good。...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

等风来不如迎风去

你的鼓励是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值