From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Where are my patches going?
Date: Thu, 29 Mar 2012 06:42:40 -0600 [thread overview]
Message-ID: <4F7458C0.5050501@mlbassoc.com> (raw)
In-Reply-To: <20120329115328.GA20337@novatech.datenfreihafen.org>
On 2012-03-29 05:53, Stefan Schmidt wrote:
> Hello.
>
> On Thu, 2012-03-29 at 05:36, Gary Thomas wrote:
>> On 2012-03-29 05:26, Andreas Oberritter wrote:
>>>
>>> On 29.03.2012 13:17, Gary Thomas wrote:
>>>> A number of times when I've sent patches to the list via 'git send-email',
>>>> they seem to never arrive. How can I figure out where they are going?
>>>
>>> your patches arrived. You can find submitted patches in OE's patchwork
>>> installation [1] or in the mailing list archive [2] some minutes after
>>> they have been sent.
>>
>> That's good to hear, but why am I not seeing them on the list?
>
> If you have been on the CC list, IIRC default option in git
> send-email, it is likely that mailman has just dropped you from the
> receiver list for these mails as you already got it in CC thus
> avoiding duplicates. Something that can be configured in
> mailman if desired.
I don't see any way to adjust this on this list - there doesn't
seem to be a "my account settings" link on the info page.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2012-03-29 12:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 11:17 Where are my patches going? Gary Thomas
2012-03-29 11:26 ` Andreas Oberritter
2012-03-29 11:36 ` Gary Thomas
2012-03-29 11:53 ` Stefan Schmidt
2012-03-29 12:42 ` Gary Thomas [this message]
2012-03-29 12:57 ` Eric Bénard
2012-03-29 13:27 ` Stefan Schmidt
2012-03-29 12:31 ` Enrico
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=4F7458C0.5050501@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-devel@lists.openembedded.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