"Henrik Grubbström (Grubba)" <grubba@xxxxxxxxxx> writes: > This is useful for repositorys not containing fully normalized files > (eg containing CRLF's or expanded $Id$ strings), where a later attribute > change implies a conversion mode change. Without this set of patches > the user would need to recommit semantically unchanged files to get > a clean index. A more fundamental (or perhaps "silly") question is if that "user would need to" is necessarily a bad thing. If the user wants to cleanse such abnormality in the recorded blobs, shouldn't there be a conscious act, iow, a commit that records that "I am fixing that mistake, and from now on, the recorded data are normalized"? Perhaps I am missing something very trivial that you have already explained to the list but I forgot amid my moving and other confusion, and if that is the case I apologize in advance ;-). -- 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