[Please don't top-post.] On Thu, May 31, 2012 at 02:21:16PM -0500, Lanny Ripple wrote: > >> Perhaps the error message in git-am could be modified to indicate > >> sed is a suspect?. E.g., > [...] > > Hrm, that does not sound an attractive way going forward. > [...] > You have three recent instances where people have bumped into this > with sed. (And yes on reporting it to the packaging project.) It > seems to me leaving a breadcrumb so that folks can figure out what's > going on without having to bother the list would be a win for > everyone. But you have to keep in mind all of the people who will be led down the wrong path by your breadcrumb when the failure is caused by a _different_ problem. What is the probability that it is helpful versus not helpful? If you are going to give advice that sed might be broken, you should at least test to see if it is broken and report it. But really, I'd rather just see the broken sed fixed. Where would the breadcrumb lead people at this point, anyway? We don't actually have a solution besides "uninstall this other, crappy sed". Has the sed bug actually been fixed? -Peff -- 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