I think if you wanted to do that, Git would have to have a concept of tracking multiple branches.. I don't think it could do that.. Because you would need to be able to do "my-patch > tracks origin/my-patch > tracks upstream/master".

I do like the idea of doing the git deepen over time.

@Alexander the scroll in the middle of the columns is exactly the same as pressing next/prev.. you do not scroll line by line, but diffs. It's very handy.

Is it not just as easy to use the scroll wheel on the middle column to jump to the changes?
I find it very annoying on GitHub where I have to keep expanding those stupid collapsed code parts.. Annoying as hell.

I too find I keep pressing Ctrl+P to "File Filter" but instead presented with the Pull Dialog..

But that is mainly because I am used to the Chrome Development Panel File Search and Eclipse. (Though, Eclipse's default is Ctrl+Shift+R, I remapped it to Ctrl+P to match Chrome.

Damn you Ed Balll.. I've had my novice users creating branches and tracking the wrong branch again.. Very fustrating.

Ahh, They put in the "Commit to Master/Container & Submodule at the same time" feature? That one totally passed me by. It was something I needed in the past, but have changed jobs and no longer needed.. If that feature is in, then I would recommend doing that.

Each "submodule" can be committed to separately (as you may be doing already". And since your "master/container" repo is not a "end product", you do not have to worry about versioning that much. It should be childs play to just have all your current repos 1 folder deeper (within a container folder/container repo).. In the smartgit interface, they would all still have the same abilities.. Just (again) 1 level deeper inside the container repo.

You can select your current repo, and then the second repo, and "Right Click > Open Repository" this will keep your open repo open and also open the second repo. Yes, if you want more than that, selecting all the open repos could become a pain

Wow, And hear I thought Grouping Commit+Submodule/Commit was going to be hard.. Completely separate repos sounds very challenging.

Yep, I would be one of them. I hate the way SourceTree/GitKrakken split the views.