> actually one bit of functionality from Git that I miss would be telling it to treat certain changes in the working copy as something that shouldn't show up as

> actually one bit of functionality from Git that I miss would be telling it to treat certain changes in the working copy as something that shouldn't show up as modified, but also not even show up as something that can be staged/committed. My guess of how git would like you to solve this problem would be with a throwaway commit that you then delete with an interactive rebase. It requires you to keep track of which commits you need to push or remove but it is doable (Actually due to a particular situation I do something very similar at my job) Which lead into what I think is a critical problem with git: lack of visualization of data; in my opinion git is unusable without a GUI because sometimes you need to juggle a few branches and you need good interactive graphical representations of a lot of the git database.