How to browse submodule in Git Extensions?

703 views
Skip to first unread message

James Johnston

unread,
Nov 4, 2011, 4:13:45 PM11/4/11
to GitExtensions
Hi,

I am trying out basic submodule functionality in Git Extensions. I
have a repository called "sub" and a repository called "super"; sub is
a submodule of super.

When I open the super repository in Git Extensions, I can view the
history of it and do normal stuff in it as usual. I would like to work
with the submodule repository. How do I do this with Git Extensions?

Under the Submodules menu, I found the promising "Browse submodule"
menu with an entry for "sub". But when I click sub, Git Extensions
only refreshes the super project repository. It doesn't switch to the
submodule repository.

Basically what I want to do is have Git Extensions show me the
submodule repository and let me do commits in it, branch it, push/pull
it, etc. How do I do that?

Best regards,

James Johnston

Arnaud

unread,
Nov 4, 2011, 5:22:03 PM11/4/11
to gitext...@googlegroups.com
Hi,

I've encoutered the same issue a few days ago. It comes from the fact that git submodule started using gitdir files for storing submodules, somewhere between version 1.7.6 and 1.7.7.

GitExtensions contains some logic to determine whether a directory contains a valid git repository. That logic doesn't support the gitdir mechanism, which is why it looks like you can't switch to the submodule repository.

I'm about to send a pull request that fix the issue (probably monday), since I would also find it useful :)

In the mean time, you can use a previous release of git/msysgit.

Regards,
-

Arkadiy Shapkin

unread,
Nov 5, 2011, 11:02:41 AM11/5/11
to gitext...@googlegroups.com

James Johnston

unread,
Nov 7, 2011, 3:44:58 PM11/7/11
to gitext...@googlegroups.com
Sounds good - poking around on GitHub seems to indicate that the pull request has already been merged with main Git Extensions master branch. Any word on when the next version of Git Extensions will come out? (I'd just as soon not worry about compiling a less stable build of Git Extensions from source, especially given that I don't even have all the tools needed to do the build.)

Best regards,

James Johnston

Reply all
Reply to author
Forward
0 new messages