Am 7/29/2011 15:19, schrieb Jakub Narebski: > Are you sure? It seems to work as I thought it would. > [...] > Notice that change to 'bar' didn't get comitted. Of course, it didn't get committed, you promised not to change it, so why should git commit it? However, your example does not show the dangerous part. git-commit is not dangerous. But you might run into trouble when git has to merge content into the worktree or index; in this case, git may decide to just read the file instead of to unpack an object - assuming that the content on disk is identical to the unpacked object (it will do so because with --assume-unchanged you promised not to change the file). If you broke your promise, you get to what you deserve ;) No code reference, sorry, because I'm just parrotting what I've read elsewhere on the list, for example, http://thread.gmane.org/gmane.comp.version-control.git/146082/focus=146353 -- Hannes -- 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