I was trying to set up my Hosting Provider, and kept getting a simple "401" error message.  My password is correct.

I switched to SourceTree to try out the same thing, and it let me know what was going on.

Can SmartGit do the same?  That would have saved me 15 minutes of retrying :)

A common operation in SG is to right-click on a specific file and choose "commit". This stages (if necessary) the specific file and prepares to commit it. 

However, if other files are already staged, they will be added to the commit even if that was not the intention. This fairly frequently causes accidental commits in our codebase, because the user assumes SG is going to commit only the selected file, but ends up committing other staged files as well because they forget to double-check the pre-commit dialog.

This is particularly common when lots of files are modified, because that can result in some staged files being "offscreen" in the "Files" window at the time the user selects the individual file. 

SmartGit already has a similar warning when someone is submitting "staged modified" files (to ask if only the staged changes should be submitted, versus all changes), so there is precedent for this kind of helpful warning.

Example: In the image below I right-clicked on the highlighted .gitignore file to commit it. If I am in a rush and forget to check the pre-commit dialog, I'll accidentally commit 3 files instead of one.

** Alternately (and perhaps ideally) SG would just disable the "submit" button when right-clicking a single file when other files are staged but not selected. This would prevent the problem entirely.

It would be nice to include tag information into commit message when merging from tag, something similar to the following:
"Merge tags/26.28.1(commit '9cfa861e02986dbed18dc83a3b3397699e3a4baf') into master"

If there are multiple tags behavior could be the same as for branches - use the first one from the list

When trying to understand the history of a change, it's common for someone to open the log window and then click back and forth on different commits to see what changed in them.

Currently, when the user clicks on a commit, the differences pane in the log window switches to display the file that is at the top of the Files window based on the current sort order. This makes it cumbersome to switch back and forth between commits to see what happened to a particular file because, unless that file happens to be at the top of the sort order in each commit, the differences pane keeps jumping around between files.

As an example, attached are two screenshots of what happens to the view when I switch between two changelists, both of which contain the same file "DBExternalViewManagerImpl.inl". 

I click on first commit and select DBExternalViewManagerImpl.inl in the files window:

Then I click on next commit in log; DBExternalViewManagerImpl.inl does not remain selected in files window, and the contents of the differences pane therefore change:

What I think the behavior should be is:

1. the file selected in the current commit should remain selected when switching to another commit, so long as the other commit contains the same file.
2. when switching to a different commit that does not contain the same file, it should switch to either:
• The file that was selected most recently for this commit
• Or the file at the top of the sort order, if no file was previously selected for the commit

#1 is the most important. #2 would really help when skipping around through multiple changelists that may not all contain the same files, but I understand that it would require a tiny amount of state tracking and may not be as easy to implement as #1.

Thanks for considering this request.

(Note: I filed this several years ago via email and it was filed internally as SG-9991. Since I cannot find it here on userecho, I have assumed it got "lost" and am re-filing it)

I regularly type "fixup! " and paste a copied hash into the commit window message box.

Since my hand is already on the mouse to click into the text box and paste the hash, it could easily click a "fixup!" button above the text box (to the right of the "Commit Message:" label) just before that and save the typing.

The Log window with the Repositories view and Branches view is a fantastic new feature.  With the Commits view now having the Working Tree and we can commit from the Log window, please add the Commit Message view to the Log window too.  I miss having the ability to pre-type commit message info as I make changes and/or stage files.

When I open Log by double-clicking on a commit in the Journal, this commit appears under Commits node in the Branches panel. Thus I can use it as a root in the commits tree. I want to be able to conveniently add any commit from the log to this list in Commits node. So that I can use any commit as a root in the commit tree.

This would be very helpful in the following scenario. I am digging down the history, find relevant commit, and then make it the root of the tree to simplify further research.

The new Log window Repo and Branches feature is fantastic.  One thing on the Repos view that I'm missing from the Working Tree window is allow to opening multiple repos

With the new Log window having the Repo and Branches views, and currently limited to "opening" only one repo at a time, is there a need to "Open Repository" on it?

I like how when cloning a repository SmartGit populates the clone url from the clipboard. What would also be nice would be if there was a --clone command line option that would launch the clone dialog using the current directory as the default location in which to create the cloned repository.

This would be especially useful as on Linux SmartGit doesn't seem to have any file manager integration so currently the only way to clone in SmartGit is to open SmartGit, launch the clone dialog, then use the folder explorer to choose where to put the cloned repo. Currently it's quicker and easier to clone using the git cli than to use SmartGit.