Timeline for answer to Git submodule update by robinspb
Current License: CC BY-SA 4.0
Post Revisions
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 28, 2024 at 16:20 | comment | added | Daniel Russell |
I thought setting a submodule branch really means, setting it to track a remote branch, but even then, I took it to mean, simply, "find the SHA1 of the remote branch of this name whenever update --remote is run and then actually set HEAD to the SHA1, not the branch ref." But apparently --merge and --rebase implicitly cause the submodule to ACTUALLY track a ref? The interface of submodules seems messy and inconsistent with the rest of git. And I feel unsure of details like this as a result.
|
|
| Jun 28, 2024 at 16:19 | comment | added | Daniel Russell |
It's very confusing to me that --merge or --rebase seem to magically also change the behavior of the HEAD for a submodule? Do I have that right? Normally, as far as I understood it, there's no direct way to tell git, "this submodule should track a ref."
|
|
| Jun 16, 2019 at 9:02 | history | edited | Peter Mortensen | CC BY-SA 4.0 |
Active reading.
|
| Jan 25, 2014 at 0:50 | history | answered | robinspb | CC BY-SA 3.0 |