Implemented in version 18.2.

So you are suggesting that selecting a continuous set of commits should be handled like selecting the first and last commit of this range?

For the Log window, it's a non-goal to mix content of several repositories in Commits or Files view. It may be beneficial in a few scenarios, but it's a confusing concept and introduces technical difficulties. If the submodules in your project are actually that interconnected, the Working Tree window is the right choice for you.

Mergable Coloring from the Commit's view hamburger menu may be helpful here.

I don't think we want to change the order as suggested by default. But untracked files could be sorted down-most if Preferences option Suggest to Add untracked files is deselected.

Why don't you ignore unversioned files? You may even ignore them only for you in .git/info/exclude

That's interesting. They write "Consider starting the commit message with an applicable emoji" ... so this is about some more formalized classification of the commit. I'm not sure whether I would like to see all that different symbols in the Log graph, but being able to quickly distinguish between e.g. feature improvements, performance improvements, bugs and refactorings sounds really useful to me.

Can you give a sample repository URL of a project which is using GitMojis? I'm wonder whether they could somehow be used in the Log graph ... 

> When you pick the "permanent option", the index (clean) does not appear when the Working Tree has changes. But it will appear when both are clean.

That's actually unexpected. For me, "Index (clean)" will always show up, regardless of the working tree state. If you can provide a small test repository for which the problem is reproducible, that would be great.