From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] linphone package
Date: Tue, 6 Mar 2012 10:36:11 +0100 [thread overview]
Message-ID: <20120306103611.4103fb9d@skate> (raw)
In-Reply-To: <FD9AD8C5375B924CABC56D982DB3A802078FA5F2@EXMB1.micrel.com>
Hello David,
Le Tue, 6 Mar 2012 00:42:58 +0000,
"Choi, David" <David.Choi@Micrel.Com> a ?crit :
> After seeing a patch submitted during the August last year, I checked
> out the latest stable version of buildroot last night. But After
> uncompressed the buildroot source tree, I could not find the patch
> applied to the package/Config.in for the linphone.
The patch at:
From: Pedro Sanchez <psanchez@fosstel.com>
To: buildroot at busybox.net
Subject: [Buildroot] [PATCH 1/1] New Package: Linphone
Date: Wed, 10 Aug 2011 10:26:34 -0400
has apparently not been applied, even though it looked quite good (but
the contributor hasn't been persistent enough by re-sending updated
versions of the patch).
Can you take the patch, update it and push it again so that we can merge
it?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-03-06 9:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 0:42 [Buildroot] linphone package Choi, David
2012-03-06 9:36 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-09 14:05 Pedro Sanchez
2011-08-09 15:21 ` Peter Korsgaard
2011-08-09 18:34 ` Pedro Sanchez
2011-08-09 18:39 ` Peter Korsgaard
2011-08-09 18:56 ` Yann E. MORIN
2011-08-09 19:25 ` Peter Korsgaard
2011-08-09 19:40 ` Yann E. MORIN
2011-08-09 19:44 ` Peter Korsgaard
2011-08-09 19:50 ` Yann E. MORIN
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=20120306103611.4103fb9d@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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