I would also find such an ability useful. Our company makes use of many individual git repos (one for each library/module, which are sorted into categories (groups) in Smartgit). Being able to right-click and say "Open Repository As Well" or "Add to open repositories" would be quite helpful.

I do not see why there would be a conflict. The format of the pattern would change depending on which .gitignore the user chooses to use, and yes, the order of precedence of the .gitignores should still prevail (as they must do in SmartGit anyway).

An example. I choose to ignore the file "doc\Doxyfiles\doxyfile.cmake":

1. If I choose to ignore using the root gitignore the result in the .\.gitignore is: "/doc/Doxyfiles/doxyfile.cmake"
2. If I choose to ignore in the current folder, the result in "doc\Doxyfiles\.gitignore" is simply "/doxyfile.cmake"

Naturally there are a number of other options that could also be provided to the user:

• Ignore recursively in sub folders
• Add the ignore to the ".git/info/exclude" file, etc

However, I am most interested in the two choices I have indicated. Currently to ignore a file using only the root .gitignore requires me to leave SmartGit and either edit the file manually (which is quite tedious if you have many files in many (sub) folders) or use an external tool (such as TortoiseGit, which while less tedious will not allow the selection of many items in the "flat" view presented by SmartGit.)