From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>,
Tom Rini <tom_rini@mentor.com>
Subject: [2011.03-maintenance] live555 update
Date: Tue, 16 Aug 2011 19:24:07 +0200 [thread overview]
Message-ID: <4E4AA7B7.7020006@dresearch-fe.de> (raw)
Is there a chance to update live555 to a newer version by cherry-picking this patch from oe-dev master?
commit b13c2ab570637b176e1411ea3db0ddf412a9f2f3
Author: Andrea Adami <andrea.adami@gmail.com>
Date: Sat Apr 23 23:57:36 2011 +0200
live555: catch up with upstream habits of upgrading and removing tarballs
Signed-off-by: Andrea Adami <andrea.adami@gmail.com>
Regards,
Steffen
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next reply other threads:[~2011-08-16 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 17:24 Steffen Sledz [this message]
2011-08-21 18:02 ` [2011.03-maintenance] live555 update Tom Rini
2011-08-22 6:20 ` [2011.03-maintenance] Pull request (live555 update) Steffen Sledz
2011-08-25 15:27 ` Tom Rini
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=4E4AA7B7.7020006@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=tom_rini@mentor.com \
/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