Comments on: Git submodules in N easy steps http://johnleach.co.uk/words/323/git-submodules-in-n-easy-steps Stuff I think, see and do Sat, 11 Feb 2012 15:56:55 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Good examples in documentation | John Leach's Blog http://johnleach.co.uk/words/323/git-submodules-in-n-easy-steps/comment-page-1#comment-157757 Good examples in documentation | John Leach's Blog Sat, 11 Feb 2012 11:51:54 +0000 http://johnleach.co.uk/words/?p=323#comment-157757 [...] my Git submodules post I name the two example projects your_project and other_project and use it consistently throughout. [...] [...] my Git submodules post I name the two example projects your_project and other_project and use it consistently throughout. [...]

]]> By: john skaller http://johnleach.co.uk/words/323/git-submodules-in-n-easy-steps/comment-page-1#comment-157409 john skaller Mon, 06 Feb 2012 08:45:35 +0000 http://johnleach.co.uk/words/?p=323#comment-157409 Solved my problem in 60 seconds.. thanks!! Solved my problem in 60 seconds.. thanks!!

]]> By: James Womack http://johnleach.co.uk/words/323/git-submodules-in-n-easy-steps/comment-page-1#comment-154222 James Womack Thu, 29 Dec 2011 05:09:29 +0000 http://johnleach.co.uk/words/?p=323#comment-154222 I've looked at about 6 submodule descriptions in the last 20 minutes and yours is the one that clicked for me. Thank you. I’ve looked at about 6 submodule descriptions in the last 20 minutes and yours is the one that clicked for me. Thank you.

]]> By: Andrew Cobby http://johnleach.co.uk/words/323/git-submodules-in-n-easy-steps/comment-page-1#comment-117546 Andrew Cobby Wed, 02 Mar 2011 04:37:42 +0000 http://johnleach.co.uk/words/?p=323#comment-117546 Be careful using tab completion with the module paths when committing. When tabbing, it will append a / (slash) to the end of the directory but this will cause Git to misinterpret the command and you will get an error: <code>error: pathspec 'lib/other_project/' did not match any file(s) known to git.</code> So make sure you remove that trailing slash! Be careful using tab completion with the module paths when committing. When tabbing, it will append a / (slash) to the end of the directory but this will cause Git to misinterpret the command and you will get an error:

error: pathspec 'lib/other_project/' did not match any file(s) known to git.

So make sure you remove that trailing slash!

]]> By: Madhava Jay http://johnleach.co.uk/words/323/git-submodules-in-n-easy-steps/comment-page-1#comment-104364 Madhava Jay Mon, 06 Dec 2010 23:58:13 +0000 http://johnleach.co.uk/words/?p=323#comment-104364 Hi John, nice post. The only problem I have with submodules is when someone makes a change to a submodule everyone else with working trees of the same main project dont get those changes on their next pull. Is there a way to enforce or opt in for that. Additionally, for some reason when people initially clone down the main project their submodule will get init and updated to a specific tag, but that leaves their submodules working tree on (no branch), which means they cant make changes or update unless they switch to master. Its easy to do that but its a pain in the ass. I would like a simple way to ensure the submodules change to the tag in the commit of their parent repo when you pull down, that way, I can make a change to a submodule and all other working trees get that change as well when they next pull down my main project commit. Does that make sense, im not sure if its even possible but it would be awesome! :) Cheers, Madhava Jay Kintek.com.au Hi John, nice post.
The only problem I have with submodules is when someone makes a change to a submodule everyone else with working trees of the same main project dont get those changes on their next pull. Is there a way to enforce or opt in for that.

Additionally, for some reason when people initially clone down the main project their submodule will get init and updated to a specific tag, but that leaves their submodules working tree on (no branch), which means they cant make changes or update unless they switch to master. Its easy to do that but its a pain in the ass.

I would like a simple way to ensure the submodules change to the tag in the commit of their parent repo when you pull down, that way, I can make a change to a submodule and all other working trees get that change as well when they next pull down my main project commit.

Does that make sense, im not sure if its even possible but it would be awesome! :)

Cheers,
Madhava Jay
Kintek.com.au

]]> By: vlkv http://johnleach.co.uk/words/323/git-submodules-in-n-easy-steps/comment-page-1#comment-64142 vlkv Sun, 20 Sep 2009 12:14:05 +0000 http://johnleach.co.uk/words/?p=323#comment-64142 nice short explanation! Thanks :) nice short explanation! Thanks :)

]]>