Re: Problems with sending patch

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Wed, 2013-01-09 at 09:54 +0100, Lukas Bulwahn wrote:
> On 01/09/2013 09:50 AM, Marko Lindqvist wrote:
> > On 9 January 2013 10:34, Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de> wrote:
> >> Hi,
> >>
> >> I have been repeated trying to send a patch to this mailing list, but it
> >> seems that it never appears here.
> >> I have checked the commit extensively for some problem, I tried different
> >> ways of sending with format-patch and thunderbird, and git-send-email.
> >> And I have checked our mail server. However, none of these options helped.
> >>
> >> I have sent patches some weeks ago already, that's why I am surprised that
> >> it does not work anymore.
> >> Has something been changed lately for sending patches on the mailing list?
> >>
> >> Any pointers are welcome.
> >   Looking my inbox, I've received at least three times this patch from you:
> > [PATCH] site/common: deactivate a runtime check for ipv6-support in,
> > python >=2.7.1 that fails when cross-compiling
> >
> >   If you still don't see them yourself, your end is probably just
> > noticing that you have sent them yourself and they should not be
> > displayed as incoming.
> >
> Thanks for your response. I did not expect my end to be that intelligent.

There is an option in mailman's config where you elect to get your own
emails to the mailing list or not. It sounds like you've elected not to.

An easy way to check if an email has got to the list is to use the
mailing list archives:

http://lists.linuxtogo.org/pipermail/openembedded-core/

Cheers,

Richard