On Friday 12 February 2016 18:24:50 Andreas Pape wrote: > Am I right that the problem comes from the e-mail client I use? Or is > there an issue with the patch as such (i.e. how I created it with git - I > tried to follow the description on open-mesh.org)?
It looks like your client in corrupting the patch. The first link should
explain how to configure some clients. Maybe you can follow the steps to
configure your client.
> I conclude from the
> error message in your mail that it's more likely that I have become a
> victim of my e-mail client.... If this is the case, I will follow the
> advice given in one of the links you refered to and send the patches to
> myself first and try out if they can be applied first before I make a
> second attempt to send them to the mailing list. Unfortunately I'm not
> allowed to use another e-mail client, but I think I can squeeze some
> settings for pure text e-mails (like automatic line breaks).
Usually the easiest way is to use git-send-email. But this would be a
different email client.
And let me guess, you have to use your phoenixcontact.com mail account to
contribute to projects... If nothing else works then maybe you can send it
just as attachments. It is a little bit ugly to comment on attachments but
better than no patches at all. (I hope it is ok for the maintainers)
> Sorry for spamming the mailing list with nonsense....
No problem. I've send more nonsense to the list than anyone else :)
> Just for my curiosity: are patches automatically applied to a repository
> if I send them to the mailing list? If this is the case, I didn't know. I
> would have been more cautious otherwise.
No, the patches are not applied anywhere automatically. Marek will go through
the patches and apply them manually after they were discussed on the
mailinglist.
Some projects use a tool called patchwork that gathers patches but even then
it wouldn't be applied in a git repo automatically.
Kind regards,
Sven
signature.asc
Description: This is a digitally signed message part.
