From: Robert B. Williams <rwilliams@valcom.com>
To: buildroot@busybox.net
Subject: [Buildroot] SVN guidance request
Date: Thu, 17 Jul 2008 11:17:04 -0400 [thread overview]
Message-ID: <487F6270.1090301@valcom.com> (raw)
I am very new to buildroot. Nice work!
Anyway, I would like some advice on how to best version control
buildroot with my work.
I was hoping to put buildroot and the multiple projects I create with it
in an SVN repository. I'll need to be able to merge releases from
buildroot from time to time while maintaining my project related
changes. I am also considering saving the downloads, in case older
versions become unavailable.
The documentation indicates that any changes made to
project_build_ARCH/root/ will be lost during a toolchain build. Does
this mean I will need to build everything once (or kill the process
after the toolchain is built) and then update my
project_build_ARCH/root/ from my repository and then build the project
again? Or is there a better approach to storing project specific root
files? I know alot of the common files could simply be stored in the
target/generic/target_skeleton but what about the ones that differ
between projects?
If there is documentation, hints, faqs, wiki, or any experience in this
areas please let me know.
In the meantime I'll start experimenting.
Cheers!
reply other threads:[~2008-07-17 15:17 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=487F6270.1090301@valcom.com \
--to=rwilliams@valcom.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