From: Jerry Kirk <jkirk865@gmail.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Advice on Directory Structure
Date: Mon, 20 Feb 2012 22:21:57 +0000 (UTC) [thread overview]
Message-ID: <loom.20120220T231704-130@post.gmane.org> (raw)
I'm looking for some advice on how to structure the source code directories of
our new embedded linux project that will rely on PTXDist. Our development will
run the full breadth including new drivers, patches to existing drivers,
applications, etc.
I've been reviewing the "practical project workspace" outlined in O'Reilly's
Building Embedded Linux Systems book. It's a fair start but not as detailed as
I had hoped. We're using some sort of cloud based DVCS system for sourc code
controla s well.
Any advice would be great to try and avoid painful restructures.
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2012-02-20 22:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 22:21 Jerry Kirk [this message]
2012-02-21 8:58 ` Josef Holzmayr
2012-02-21 16:08 ` Jerry Kirk
2012-02-21 16:36 ` Josef Holzmayr
2012-02-21 17:58 ` Jerry Kirk
2012-02-21 9:39 ` Alexander Dahl
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=loom.20120220T231704-130@post.gmane.org \
--to=jkirk865@gmail.com \
--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