From: vmalkani <vmalkani@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] automated building of Opkg repository
Date: Mon, 3 Feb 2014 11:11:17 -0800 (PST) [thread overview]
Message-ID: <1391454677012-61317.post@n4.nabble.com> (raw)
In-Reply-To: <1391454473-6735-1-git-send-email-vmalkani@gmail.com>
Hi,
I updated the patch to work with Description and Version correctly (These
were causing compilation errors).
In addition, I updated the patch to apply cleanly to pre-generic.mk
I'm not sure if this is the correct process so I hope this is the correct
way to do it.
Vinay
--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/automated-building-of-Opkg-repository-tp61315p61317.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
next prev parent reply other threads:[~2014-02-03 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Add support for automated building of Opkg repository>
2014-02-03 19:07 ` [Buildroot] automated building of Opkg repository Vinay Malkani
2014-02-03 19:07 ` [Buildroot] [PATCH] automated opkg repository building. Fixes Version, Description, and pkg-generic.mk Vinay Malkani
2014-02-03 19:11 ` vmalkani [this message]
2014-02-03 21:42 ` [Buildroot] automated building of Opkg repository Thomas Petazzoni
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=1391454677012-61317.post@n4.nabble.com \
--to=vmalkani@gmail.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 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.