* Problems with sending patch
@ 2013-01-09 8:34 Lukas Bulwahn
2013-01-09 8:50 ` Marko Lindqvist
0 siblings, 1 reply; 4+ messages in thread
From: Lukas Bulwahn @ 2013-01-09 8:34 UTC (permalink / raw)
To: openembedded-core
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.
Lukas
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Problems with sending patch
2013-01-09 8:34 Problems with sending patch Lukas Bulwahn
@ 2013-01-09 8:50 ` Marko Lindqvist
2013-01-09 8:54 ` Lukas Bulwahn
0 siblings, 1 reply; 4+ messages in thread
From: Marko Lindqvist @ 2013-01-09 8:50 UTC (permalink / raw)
To: Lukas Bulwahn; +Cc: openembedded-core
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.
- ML
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Problems with sending patch
2013-01-09 8:50 ` Marko Lindqvist
@ 2013-01-09 8:54 ` Lukas Bulwahn
2013-01-09 12:45 ` Richard Purdie
0 siblings, 1 reply; 4+ messages in thread
From: Lukas Bulwahn @ 2013-01-09 8:54 UTC (permalink / raw)
To: Marko Lindqvist; +Cc: openembedded-core
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.
Lukas
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Problems with sending patch
2013-01-09 8:54 ` Lukas Bulwahn
@ 2013-01-09 12:45 ` Richard Purdie
0 siblings, 0 replies; 4+ messages in thread
From: Richard Purdie @ 2013-01-09 12:45 UTC (permalink / raw)
To: Lukas Bulwahn; +Cc: openembedded-core
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-01-09 13:00 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-01-09 8:34 Problems with sending patch Lukas Bulwahn
2013-01-09 8:50 ` Marko Lindqvist
2013-01-09 8:54 ` Lukas Bulwahn
2013-01-09 12:45 ` Richard Purdie
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox