From: Jon Ringle <jon@ringle.org>
To: "Jürgen Beisert" <jbe@pengutronix.de>
Cc: "Olbrich, Michael" <m.olbrich@pengutronix.de>, ptxdist@pengutronix.de
Subject: Re: [ptxdist] git ptxdist best practices
Date: Wed, 8 Jan 2014 09:14:26 -0500 [thread overview]
Message-ID: <CAMwGMjzYfpvMOurOibf1G=uT_fM5iazGtr_zeRsqgXQfJDi8KQ@mail.gmail.com> (raw)
In-Reply-To: <201401080859.43988.jbe@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1065 bytes --]
On Wed, Jan 8, 2014 at 2:59 AM, Jürgen Beisert <jbe@pengutronix.de> wrote:
> Hi Jon,
> Do you want to use this BSP only by your own, or is it intended to provide
> it
> to other developers who use it as a base for their own work?
>
> In the latter case I would "release" the various components and create
> archives
> of it. And these archives can simply be part of the (finally) released BSP
> you
> provide to other developers (in contrast to the downloadable archives
> PTXdist
> uses for the remaining packages like Busybox, Qt and so on).
>
> Yes, this will be for other developers to base their work off of.
So, what exactly would be included in the "release" BSP?
platform/sysroot-*/ and platform/root*/ ??
> If you still want to use git repositories for the external components we
> should
> wait for Michael, because he can explain how to use the PTXdist feature
> which
> deals with such repositories.
>
> Yes, I'd like to understand better ptxdist features to support externat
components maintained by our own git repos :)
[-- Attachment #1.2: Type: text/html, Size: 1573 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-01-08 14:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 2:32 Jon Ringle
2014-01-08 5:56 ` Alexander Dahl
2014-01-08 6:12 ` Jon Ringle
2014-01-08 9:21 ` Alexander Dahl
2014-01-08 9:48 ` Alexander Dahl
2014-01-08 9:52 ` Jürgen Beisert
2014-01-08 17:56 ` Jon Ringle
2014-01-08 20:43 ` Alexander Dahl
2014-01-08 7:59 ` Jürgen Beisert
2014-01-08 14:14 ` Jon Ringle [this message]
2014-01-09 8:10 ` Jürgen Beisert
2014-01-09 9:03 ` Olbrich, Michael
2014-01-09 15:23 ` Jon Ringle
2014-01-09 16:06 ` Michael Olbrich
2014-01-09 16:37 ` Jon Ringle
2014-01-10 15:37 ` Michael Olbrich
2014-01-10 15:41 ` Jon Ringle
2014-01-11 1:47 ` Jon Ringle
2014-01-24 9:21 ` Michael Olbrich
2014-01-24 13:10 ` Jon Ringle
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='CAMwGMjzYfpvMOurOibf1G=uT_fM5iazGtr_zeRsqgXQfJDi8KQ@mail.gmail.com' \
--to=jon@ringle.org \
--cc=jbe@pengutronix.de \
--cc=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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