jung-kim

I'm having very hard time following what is being described here. Are you suggesting that when you add new branch via `+` you expect that branch to be created at...

two settings you can set at `~/.ungitrc`. ``` { logGitCommands: true, logLevel: 'info' } ``` also, you might be at the [headless state](https://medium.com/north-arrow-research/git-tips-what-is-a-headless-state-daa9bc4e1d5a). Can you try doing `git checkout master`...

Right, I guess your checked out node is behind the latest node in remote or other sources. You could set `maxActiveBranchSearchIteration` to 300 or something like that within `.ungitrc` to...

Precisely. Right now stash button stash them all. But stashing only the ones that are check marked would be preferable. I will probably implement it today and show you what...

I was afraid of that might be the case. I even thought of a hack where temporary check in unselected, stash and revert.

-p would have been great but it doesn't work with untracked items. So if there are any new files it wouldn't work. And -p would be per changes, not per...

So for that one you want to increase `maxActiveBranchSearchIteration` config value to be a positive number. That number represents number of iterations it may attempt in search for the active...

Problem with that is that we don't know any details of the "active branch" until checkout git node is parsed. By that time we would have all of it's ancestors...

Not all repos can fit

If we just loaded hashes of all commits into memory, what problem does that solve?