From: Sven Eckelmann <sven@narfation.org>
To: Andreas Pape <APape@phoenixcontact.com>, b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Antwort: Re: [PATCH 1/4] batman-adv: Prevent mutliple ARP replies sent by gateways in bla setups with dat enabled
Date: Fri, 12 Feb 2016 18:36:46 +0100 [thread overview]
Message-ID: <4010815.oxNa1dpjBe@sven-edge> (raw)
In-Reply-To: <OFD4FAC06D.50E7ADCE-ONC1257F57.005D7B39-C1257F57.005FA7D8@phoenixcontact.com>
[-- Attachment #1: Type: text/plain, Size: 1978 bytes --]
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
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-12 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 13:51 [B.A.T.M.A.N.] [PATCH 1/4] batman-adv: Prevent mutliple ARP replies sent by gateways in bla setups with dat enabled Andreas Pape
2016-02-12 14:47 ` Sven Eckelmann
[not found] ` <OFD4FAC06D.50E7ADCE-ONC1257F57.005D7B39-C1257F57.005FA7D8@phoenixcontact.com>
2016-02-12 17:36 ` Sven Eckelmann [this message]
2016-02-15 8:50 ` Simon Wunderlich
2016-02-15 9:11 ` Sven Eckelmann
2016-02-15 9:39 ` [B.A.T.M.A.N.] Antwort: " Andreas Pape
2016-02-15 10:08 ` Sven Eckelmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4010815.oxNa1dpjBe@sven-edge \
--to=sven@narfation.org \
--cc=APape@phoenixcontact.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).