On Fri, 2011-09-09 at 12:03 -0400, Joey Hess wrote: > It might be worth ameloriating that attack by making git log always > show the full buffer. Or it would be easy to write a tool that finds > any commits that have a NULL in their message. Just be aware that fixing the problem by diallowing NULLs in the commit message makes it impossible to include UTF-16 text in the commit message (which isn't currently handled very well anyway). Granted, I'm not sure what the most decent way of dealing with that otherwise might be as I've not taken the time to think about it... -- -Drew Northup ________________________________________________ "As opposed to vegetable or mineral error?" -John Pescatore, SANS NewsBites Vol. 12 Num. 59 -- 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