Timeline for Git update submodules recursively
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 17, 2019 at 18:51 | history | edited | drewag | CC BY-SA 4.0 |
deleted 3 characters in body
|
| Feb 24, 2015 at 16:58 | history | edited | Mark Amery | CC BY-SA 3.0 |
capitalization. And yeah, fair play with your edit - I'll try to track down some information about when the change occurred
|
| Feb 24, 2015 at 16:53 | comment | added | drewag | @MarkAmery, I remember this being a problem in some version of git that I cannot remember. I just tested it in 1.9.3 and the problem does not seem to exist anymore. I updated the answer to refer to a vague "older versions". If anyone can specify which version changed this behavior, that would be great. | |
| Feb 24, 2015 at 16:48 | history | edited | drewag | CC BY-SA 3.0 |
added 32 characters in body
|
| Feb 24, 2015 at 14:06 | comment | added | Mark Amery |
@Irineau The note about already-initialized submodules not being updated if --init is used does not match my experiences on Git 2.2.2. I see both top-level and nested submodules that have already been initialized getting the correct commit checked out when I use git submodule update --init --recursive, and I think the claim that you need to run the command with and without --init is simply wrong. Unless somebody can either show evidence that this is the behaviour or demonstrate that it's changed between versions and was once true, I plan to edit it out altogether.
|
|
| Mar 17, 2014 at 8:46 | history | edited | Fluffy | CC BY-SA 3.0 |
added 1 characters in body
|
| S Feb 28, 2014 at 13:19 | history | suggested | lrineau | CC BY-SA 3.0 |
Specify the role of --init
|
| Feb 28, 2014 at 13:17 | review | Suggested edits | |||
| S Feb 28, 2014 at 13:19 | |||||
| Sep 26, 2013 at 13:30 | comment | added | William Entriken | Is this different than my way below? | |
| Apr 16, 2012 at 13:37 | comment | added | drewag | You can just do a "git submodule add blah" and then "git submodule update --init --recursive". | |
| Apr 16, 2012 at 5:19 | vote | accept | complez | ||
| Apr 16, 2012 at 4:48 | comment | added | complez | How about recursive add submodule? "git submodule add FrameworkA.git" just pull files of FrameworkA. | |
| Apr 16, 2012 at 4:24 | history | answered | drewag | CC BY-SA 3.0 |