Linus Torvalds <torvalds@xxxxxxxx> writes: > Well, with the new-and-improved builtin "git add", you could probably do > something like the appended (on top of my most recent patch). > > It says > > No added files - did you perhaps mean to do a 'git update-index'? > > whenever it finds that "git add" has ignored a file and not actually added > anything. That, btw, can happen either because it refused to see the file > in the first place (ie it was ignored), or because all the files listed > were already added. > > In both cases the warning may or may not be sensible. > > Anyway, I dunno. I don't have any strong opinions on this. If you give a pattern that would match two files but one of them were hidden by .gitignore, this approach would not help you much. Even if we wanted to say something like "if the user explicitly tells us to add etc/mtab~ by spelling it out, we should ignore *~ entry in .gitignore", the shell expansion bites us because it is done before we get to what the user give us. We cannot distinguish that with the user typing etc/?tab* for example. If somebody (Jakub, perhaps?) cares strong enough, we could show by default "matched the pathspec but ignored by .gitignore" paths with fprintf(stderr, "ignoring '%s'\n"), and have an option -q to squelch it. I do not have strong feeling on this, so I'll see if somebody comes up with a better implementation. - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html