Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Where are my patches going?
Date: Thu, 29 Mar 2012 05:36:36 -0600	[thread overview]
Message-ID: <4F744944.7070701@mlbassoc.com> (raw)
In-Reply-To: <4F7446F9.9090304@opendreambox.org>

On 2012-03-29 05:26, Andreas Oberritter wrote:
> Hi Gary,
>
> 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?

Also, I did send these same patches last week (I still had the same
command line in the same window as I used today!) and they did not
make it to patchwork at all.  These were sent 2012-03-23 15:30 GMT +/-

>
> Regards,
> Andreas
>
> [1] http://patches.openembedded.org/patch/24811/
>      http://patches.openembedded.org/patch/24813/
>
> [2] http://thread.gmane.org/gmane.comp.handhelds.openembedded

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------



  reply	other threads:[~2012-03-29 11:45 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 [this message]
2012-03-29 11:53     ` Stefan Schmidt
2012-03-29 12:42       ` Gary Thomas
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=4F744944.7070701@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