# Is there any reason for the core/extras submodules diff between v1 and v2?

**URL:** <https://forum.ansible.com/t/is-there-any-reason-for-the-core-extras-submodules-diff-between-v1-and-v2/18514>\
**Category:** Ansible Developer\
**Created:** [June 16, 2015, 11:53am UTC](https://forum.ansible.com/t/is-there-any-reason-for-the-core-extras-submodules-diff-between-v1-and-v2/18514 "2015-06-16T11:53:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Trond\_Hindenes](https://avatars.discourse-cdn.com/v4/letter/t/96bed5/32.png) [@Trond\_Hindenes](https://forum.ansible.com/u/Trond_Hindenes)\
**Post date:** [June 16, 2015, 11:53am UTC](https://forum.ansible.com/t/is-there-any-reason-for-the-core-extras-submodules-diff-between-v1-and-v2/18514/1 "2015-06-16T11:53:16Z")

</div>

(please note that I’m no git expert)  
I just noticed that when cloning the Ansible project that submodule commits differ between v1 and v2:

Is there any reason for not having v1 up to date with the newest module repos?

Submodule path ‘lib/ansible/modules/core’: checked out ‘ **9acc7c402f729748205e78f2b66b8f25b7552e37** ’  
Cloning into ‘lib/ansible/modules/extras’…  
remote: Counting objects: 23256, done.  
remote: Total 23256 (delta 0), reused 0 (delta 0), pack-reused 23256  
Receiving objects: 100% (23256/23256), 6.32 MiB | 3.99 MiB/s, done.  
Resolving deltas: 100% (15347/15347), done.  
Checking connectivity… done.  
Submodule path ‘lib/ansible/modules/extras’: checked out ‘ **2f967a949f9a45657c31ae66c0c7e7c2672a87d8** ’  
Cloning into ‘v1/ansible/modules/core’…  
remote: Counting objects: 24991, done.  
remote: Compressing objects: 100% (243/243), done.  
remote: Total 24991 (delta 52), reused 0 (delta 0), pack-reused 24748  
Receiving objects: 100% (24991/24991), 7.17 MiB | 6.85 MiB/s, done.  
Resolving deltas: 100% (16440/16440), done.  
Checking connectivity… done.  
Submodule path ‘v1/ansible/modules/core’: checked out ‘ **f8d8af17cdc72500af8319c96004b86ac702a0a4** ’  
Cloning into ‘v1/ansible/modules/extras’…  
remote: Counting objects: 23256, done.  
remote: Total 23256 (delta 0), reused 0 (delta 0), pack-reused 23256  
Receiving objects: 100% (23256/23256), 6.32 MiB | 4.01 MiB/s, done.  
Resolving deltas: 100% (15347/15347), done.  
Checking connectivity… done.  
Submodule path ‘v1/ansible/modules/extras’: checked out ‘ **495ad450e53feb1cd26218dc68056cc34d1ea9ff** ’

---

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [June 16, 2015, 12:11pm UTC](https://forum.ansible.com/t/is-there-any-reason-for-the-core-extras-submodules-diff-between-v1-and-v2/18514/2 "2015-06-16T12:11:05Z")

</div>

Some v2 modules, specifically “command”, are not compatible with the v1 code base.

Setting them to the same would mean anyone wishing to use the command module with v1 would be unable to do so.