prashant Nidgunde <pashnidgunde@xxxxxxxxx> writes: [cc: stefan, for his interest in improving 'git submodules'] > Hello, > > I am new to this community ,so please ignore if I am asking anything silly. > > Case : > Today when I built my submodule , and did a git status , it shows as modified. > > After reading certain suggestions on web i found out that i can ignore > that adding a line in .gitmodules > > But, I had to add that line manually ( which could be errorprone > because of typos ) > > > Question: > 1. Is it feasible to build a feature like : > git submodule "zlib" ignore dirty ( which will > ignore submodule zlib when its built and dirty as it has new files in > its directory) How does it prevent you from saying git submodule "glib" ignore dirty when you really meant "zlib"? How is the command supposed to know that you did *not* mean "glib", which may currently not exist in the index nor in the working tree yet but you are about to create, and doing the "ignore dirty" configuration as an earlier step of multiple steps to add a submodule? I personally doubt that the main issue you should be concerned about is feasibility. A larger issue is how it is supposed to help, iow, is such a "feature" useful in the first place? Whenever you hear yourself say "I have to do X manually, and I can make mistakes. Can a command do it instead?", you have to ask yourself: what pieces of information do you give to that command, and how do you ensure you do not make typos on that command line? Besides, the above syntax would not work. What would a user do when a submodule called "add" exists, for example?
