On Thu, Oct 25, 2012 at 05:01:49AM -0400, Jeff King wrote: > > Hmm. What is this patch on top of? It looks like it is on top of your > original patch, but when I tried it on top of that, it does not apply > either, and the index lines in the patch do not mention a sha1 that I do > not have. Sorry, it's against km/send-email-compose-encoding (or current next) + "git-send-email: use compose-encoding for Subject". > > Do you mind re-rolling a final 2-patch series with: > > 1. Your original patch and this one squashed together, with an > appropriate commit message. I think that it's better to do refactoring and fix for ASCII in separate patches. Maybe we should reverse order of first two patches. This first will do refactoring and the second will just replace quote_rfc2047() with quote_subject() in "broken" encoding case and add test for this problem. > > 2. The second "quote when we see '=?'" patch. > > Thanks. > > -Peff ok, I will resend the final series. I need also to fix "git-send-email: use compose-encoding for Subject" patch. Now it's depends both on this series and km/send-email-compose-encoding branch. Krzysiek -- 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