I thought I knew what I was doing, after reading the instructions.
When I checked out an older version of the main project, I have to sync to the proper (older) version of the submodule too. git admonished me to run the command from the toplevel of the working tree, and when that was done,
git submodule update
gives no output.
git submodule status
shows "-8441e..." which is the SHA1 of the version I expect I need. But git status shows me that the submodule is modified. git gui shows
@ -1 +1 @@
-Subproject commit 8441ea2e54fa2e8a4f45240a0d399f1c775a1789
+Subproject commit bc47be2d623cbca83701d9f30a18fab6271dd38f
and gitk, run from the subproject's subdirectory, shows that bc47b, the newer stuff, is still active. Browsing the files, I see this is indeed the case.
Now, my impression was that 'git submodule update' was supposed to check out the proper version, namely 4441e, not merely do nothing without even an error. What am I missing?
--John
git version 1.6.5.1.1367.gcd48
msysgit on Windows XP 64-bit
=======================Sorry for the long footer; it's not my idea.
TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
--
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