From: akuster808 <akuster808@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>
Subject: Re: jethro-next merge
Date: Tue, 17 May 2016 15:17:44 -0700 [thread overview]
Message-ID: <573B9888.2080403@gmail.com> (raw)
In-Reply-To: <CA+chaQere0t5x397taYZspvW=7j9PgepFPgG82X=io-srn0XKw@mail.gmail.com>
On 05/17/2016 02:34 PM, Martin Jansa wrote:
> Just waiting for the request :)
So I have ask twice? Once from my initial pull request and another to
move from next to stable? I will make a note for next time.
thanks,
Armin
>
> On Tue, May 17, 2016 at 11:23 PM, akuster808 <akuster808@gmail.com> wrote:
>
>> Any ETA on when jethro-next will be merged to jethro? its been three weeks.
>>
>> regards,
>> Armin
>>
>
next prev parent reply other threads:[~2016-05-17 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 21:23 jethro-next merge akuster808
2016-05-17 21:34 ` Martin Jansa
2016-05-17 22:17 ` akuster808 [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-19 14:00 akuster808
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=573B9888.2080403@gmail.com \
--to=akuster808@gmail.com \
--cc=martin.jansa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.