From: jeff angielski <jeff@theptrgroup.com>
To: buildroot@busybox.net
Subject: [Buildroot] Integrating buildroot with source control tools
Date: Tue, 24 Feb 2009 09:04:03 -0500 [thread overview]
Message-ID: <1235484243.27200.11.camel@penguin> (raw)
How are people integrating their buildroot environments with their
source control tools?
Are you downloading all of the source (make source) and then putting the
entire dl tree under software configuration managemet (SCM)?
Are you creating a local server to house the packages and download from
that server? Of course putting those packages under SCM on that server?
Or perhaps are you overriding the download commands and perhaps changing
it to git pull or svn checkout?
--
Jeff Angielski
The PTR Group
www.theptrgroup.com
reply other threads:[~2009-02-24 14:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1235484243.27200.11.camel@penguin \
--to=jeff@theptrgroup.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