Martin Koegler, Mon, Sep 10, 2007 09:13:39 +0200: > > P.S. Alternatively, git-commit can be extended. It has all the > > information needed to create the fact (the tree pointed by HEAD and > > the name(s) of the file to remove from the tree). But I afraid it will > > break someones workflow unless guarded by a new flag: > > > > $ git commit --force-remove -- file > > What should break, if we can commit a by git-rm removed file (file not > in index, but in HEAD) without a special flag? The workflow of people _expecting_ it to fail for not-existing files. Besides, git commit expects not the file names but globs - 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
