On Sun, Sep 09, 2007 at 11:49:42PM +0200, Alex Riesen wrote: > No easy solution, not with removing a file. You better be careful. I found out, that cg-commit can do this. > There are hard ways if you insist on doing this all the time: [...] > > The problem is that the index and a working tree with a removed file > are actually _without_ something. There is no special fact to commit, > like there is when something changed or added. To me, this seems to be a limitation of the current implementation. There is something to commit: a new tree without an entry for a file. > 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? In CVS, you can do: rm $file cvs remove $file cvs commit $file mfg Martin Kögler - 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
