From: "Petr Štetiar" <ynezz@true.cz>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 4/6] Add recipes for building TS75xx userspace utilities
Date: Sat, 2 Apr 2011 10:40:25 +0200 [thread overview]
Message-ID: <20110402084025.GD2681@ibawizard.net> (raw)
In-Reply-To: <BA1E2EAB-64FF-47E0-AB46-407D19D68B6D@gmail.com>
Sachin Kamboj <v2g.udel@gmail.com> [2011-03-30 12:55:35]:
> We'll discuss this with the vendor - however, can we include these tarballs
> in the interim?
Maybe, that you can skip the vendor part, make GitHub account, add all the
files in one project and make ts75xx-utils versioned package and recipe. I
don't see any point why it should be in separate recipe. It's possible to make
different packages from one recipe.
-- ynezz
next prev parent reply other threads:[~2011-04-02 8:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 14:07 [PATCH 1/6] Add support for the Technologic Systems TS7500 ARM SBCs UDel V2G Team
2011-03-30 14:07 ` [PATCH 2/6] Allows the use of the angstrom distribution with ARM cores that do not support THUMB_INTERWORK instructions UDel V2G Team
2011-03-30 15:04 ` Koen Kooi
2011-03-31 20:57 ` Khem Raj
2011-03-30 14:07 ` [PATCH 3/6] Add kernel support for the Technologic Systems TS7500 ARM SBCs UDel V2G Team
2011-03-30 14:45 ` Marcin Juszkiewicz
2011-04-02 8:53 ` Petr Štetiar
2011-03-30 14:07 ` [PATCH 4/6] Add recipes for building TS75xx userspace utilities UDel V2G Team
2011-03-30 14:40 ` Marcin Juszkiewicz
2011-03-30 16:55 ` Sachin Kamboj
2011-04-02 8:40 ` Petr Štetiar [this message]
2011-03-30 14:07 ` [PATCH 5/6] Added images for the TS7500 ARM SBCs UDel V2G Team
2011-03-30 14:33 ` Marcin Juszkiewicz
2011-03-30 14:07 ` [PATCH 6/6] Adds custom defconfigs for Technologic Systems " UDel V2G Team
2011-03-31 21:00 ` Khem Raj
2011-03-30 14:43 ` [PATCH 1/6] Add support for the " Marcin Juszkiewicz
2011-03-31 20:48 ` Khem Raj
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=20110402084025.GD2681@ibawizard.net \
--to=ynezz@true.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox