> You keep sending a broken patch. I've queued v7 and replaced with v8 and > both times I had to fix them in my editor. Oh, thanks for telling me- I should make sure that my future patches aren't broken. Can someone tell me what I'm doing wrong? Earlier, Junio also had a problem with one of my patches being corrupt. I used git-imap-send and the GMail web interface to fill out the "to", "cc" and some comments. > I'm not replacing v8 with this tonight, as my pre-push test cycles are > already running (finished in one vm and continuing in another). Okay, no issues. > Please > check what I queued and make sure your future patches applies on top of > what I have. Right, so you can just squash them. Also, I think I'm sending in patches too fast so I'll slow down and rebase them on top of `pu` every time. Do tell me anything else that I can do to make my patches easier to review and apply in future. -- Ram -- 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