Steven Grimm <koreth@xxxxxxxxxxxxx> writes: > Junio C Hamano wrote: > >> Suppressing output is understandable and probably is a useful >> thing to do, but I do not see a justification to tie that >> quietness to making the status unuable... > > The status is unusable as is, actually, for the particular use case of > cg-admin-rewritehist. If you try to use git-rm as an index filter, > cg-admin-rewritehist will stop running as soon as you hit a revision > that doesn't contain the file you're looking to filter out. (If the > file doesn't exist in the first revision in your repo, that means it > will do no work at all.) Probably "git-grep foo" wouldn't be suitable as the index filter for admin-rewritehist, either, nor "git-fsck", nor many other things. What does it have to do with anything? Saying "git rm --quiet foo" from the command line, wishing to supress the output, is very understandable. Saying "git rm --ignore-unmatch foo bar baz", wishing to remove bar (which exists) even when foo does not exist, is also very understandable. I think they are pretty much independent options. - To unsubscribe from this list: 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