Re: Changing branches in supermodule does not affect submodule?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jens Lehmann:

just calling "git submodule update" every time you want the submodule to be updated according to the state committed in the superproject will do the trick (but keep in mind that all referenced commits have to be accessible in the local clone of your submodule, so you might have to do a fetch there once in a while).

Is it possible to automate this from a hook or something else? Basically, I would like it to update all the submodules to the state recorded in the commit I move to, if they were in a clean state before I moved. I do not want it to change states if I do something like

  cd submodule
  # do some changes
  git commit
  cd ..
  git checkout -b newbranch

because there I want the commit I made to the submodule to be recorded on the new branch I created. But then it was in a dirty state before I created the branch anyway, so that shouldn't be a problem.

--
\\// Peter - http://www.softwolves.pp.se/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]