Danny Auble <[email protected]> writes: > Currently it is an unknown problem that altered Par's patches the way it > did. It seems to happen at odd times. We were hoping the update we > just applied yesterday would of fixed the issue. But it seems it hasn't.
One clue might be the lines about unubscribing from the list that was added to the beginning of the mail body. Those two lines have correct newline encodings, but lines after that have been modified. Injecting text in the message is not a good idea, and it looks as you have already disabled it. Another strange thing is that delivery of my 5 mails was spread out over 2 hours, even though I sent them within seconds using git-send-email. When we are already 8 time zones apart adding an extra delay like this is rather bad for our collaboration. Secondly, the mail Date headers have been rewritten to the time of delivery in UTC-7. I am not in UTC-7, at least not most of the time, and would like list mail to keep the date that they were sent. Is it possible to fix this? > I know some like to see patches inline, but that is not the case for > me. I much prefer patches as attachments. If people choose not to use > the our bugzilla to submit patches attaching them to the email instead > of putting them inline would perhaps at least avoid the random > occurrence Par saw when sending his patches out. My main reason for sending patches inline is that this workflow is very convenient when using git, thanks to git-sent-email and git-am as Mark have already mentioned. Another git-friendly method is to use pull requests. It appears that git-send-email does have an --attach option, but I have not tried using it. Creating patch-files and uploading to a web based bug tracker is much less convenient IMHO, although I think it is probably good to have that alternative available for those who prefer that workflow. Regards, Pär
