[Buildroot] Buildroot and version control systems

Vornefeld, Bernhard Bernhard.Vornefeld at mep.de
Mon Oct 5 08:01:44 UTC 2009


Hi,

My request was rather basic: Which parts of the "used" (make etc.) buildroot subfolder structure can be versioned?
Which files and folders have to be ignored doing check ins?
Does it make sense to use the complete toolchain as working copy? 
Vendor branches are not in our scope now.

Regards, 
Bernhard

MEP Kutsch GmbH & Co. KG 
Flaßkuhle 1 
58452 Witten 
Tel.:  02302 28262-36 
Fax.: 02302 28262-99 

mailto:bernhard.vornefeld at mep.de 

http://www.mep.de 


-----Ursprüngliche Nachricht-----
Von: Will Newton [mailto:will.newton at gmail.com] 
Gesendet: Freitag, 2. Oktober 2009 15:14
An: Jonathan dumaresq
Cc: Vornefeld, Bernhard; buildroot at busybox.net
Betreff: Re: [Buildroot] Buildroot and version control systems

On Fri, Oct 2, 2009 at 2:10 PM, Jonathan dumaresq <jdumaresq at cimeq.qc.ca> wrote:
> Hi Will,
>
>
> I think this is how most people use buildroot - taking the upstream 
> version and making local modifications. It should be fairly 
> straightforward to do this in any version control system using e.g. in 
> CVS a vendor branch, or in git having two branches, one to track 
> upstream and one for your changes.
>
> We are using svn as source version control.

Subversion has some notion of vendor branches, e.g.:

http://svnbook.red-bean.com/en/1.1/ch07s05.html

But I am not an svn expert so I can't really help with the details.


More information about the buildroot mailing list