From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v0] Add support for automated building of Opkg repository
Date: Thu, 17 Jan 2013 13:54:18 +0100 [thread overview]
Message-ID: <20130117135418.2a4760e9@skate> (raw)
In-Reply-To: <1423867.kLX9PqGxu5@sagittae>
Dear J?r?me Pouiller,
On Thu, 17 Jan 2013 11:23:17 +0100, J?r?me Pouiller wrote:
> I am surprised to have any reply to this patch proposal. Patches have
> been correctly sent? (I didn't receive them but I am sure it come
> from my local mailer daemon since they appear on gmame). Or I am just
> too impatient?
Patches have been received. I intend to give a reply to them, but I
need a bit of time to do so. I'll get back with my comments soon.
Best regards,
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:[~2013-01-17 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 16:47 [Buildroot] [PATCH v0] Add support for automated building of Opkg repository Jérôme Pouiller
2013-01-15 16:47 ` [Buildroot] [PATCH 1/3] Add an entry in images sub-menu for ipk repository building Jérôme Pouiller
2013-01-15 16:47 ` [Buildroot] [PATCH 2/3] Add main scripts for opkg " Jérôme Pouiller
2013-01-15 16:47 ` [Buildroot] [PATCH 3/3] Add parsing of Config.in in ipk-post.sh Jérôme Pouiller
2013-01-17 10:23 ` [Buildroot] [PATCH v0] Add support for automated building of Opkg repository Jérôme Pouiller
2013-01-17 12:54 ` Thomas Petazzoni [this message]
2013-01-17 14:39 ` Jérôme Pouiller
2013-02-13 21:43 ` Carsten Schoenert
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=20130117135418.2a4760e9@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