Paul Betts <paul@xxxxxxxxxxxxx> writes: > ## Proposed Mitigation > > For an initial mitigation plan, I'd like to propose adding a warning to either > git clone or git checkout, that if invalid UTF-8 strings are detected, a > warning is printed to the user. > > However, without an actionable solution, it's not much of a help other than to > suggest that they downgrade to a lower version of Git. Hmph, I do not see a reason to make a huge molehill in this. The pathnames are of unspecified encoding, and if a project declares that they always use UTF-8, that would be great. Older history may need to be rewritten but that is a given. Wouldn't a flag day event per project that runs filter-branch and have participants restart their repositories be sufficient? Why does git itself have to do anything about it, and how would it help users without hurting other git users who are not involved in such a project? -- 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