From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Miss patches in patch queue
Date: Fri, 26 Feb 2010 11:02:26 -0800 [thread overview]
Message-ID: <20100226190226.GA25079@gmail.com> (raw)
In-Reply-To: <4B7920DA.8000302@dresearch.de>
On (15/02/10 11:24), Steffen Sledz wrote:
> Steffen Sledz wrote:
> > As mentioned in thread
> > <http://thread.gmane.org/gmane.comp.handhelds.openembedded/29964> i
> > miss all the patches i sent according to this thread in the patch
> > queue. :(
> >
> > Is this a mistake of mine or is there a patchwork problem?
>
> Ping
Strange. If they got applied then you may not see them in the list
otherwise patchwork might have gone AWOL when you sent them.
-Khem
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2010-02-26 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 7:08 Miss patches in patch queue Steffen Sledz
2010-02-15 10:24 ` Steffen Sledz
2010-02-26 19:02 ` Khem Raj [this message]
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=20100226190226.GA25079@gmail.com \
--to=raj.khem@gmail.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