Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: buildroot@busybox.net
Subject: [Buildroot] development environment
Date: Fri, 18 Dec 2009 09:10:58 +0800	[thread overview]
Message-ID: <20091218011058.GJ28375@buzzloop.caiaq.de> (raw)
In-Reply-To: <87fx7946jc.fsf@macbook.be.48ers.dk>

On Thu, Dec 17, 2009 at 10:47:19PM +0100, Peter Korsgaard wrote:
>  Marcel> I'm trying to create a workable environment to work with
>  Marcel> buildroot for the following :
> 
>  Marcel> I use a stable buildroot (which I may regularly upgrade) and
>  Marcel> will be adding kernel modules, board configurations and
>  Marcel> packages for my own design.  The documentation is very clear
>  Marcel> how to add the packages, so that's no issue.
> 
>  Marcel> The issue I have is that I want to use CVS for my own developed
>  Marcel> files and need to set up a workable environment to work
>  Marcel> efficiently to create patches for buildroot.
> 
> We're almost in 2010 - Are you really sure you want to do development
> with CVS today?
> 
> I've been using a similar setup like your with subversion and git
> without any big issues.

I'd also suggest using git for this purpose. Clone the master branch,
fork off your own development branch and add your packages there. You
can then keep your master in sync with the upstream repository and
rebase your own branch, merge the master or cherry-pick selected
commits.

We do something similar for own projects, and it works wonderfully.

And once you got used to git, you'll never want to get back to CVS,
believe me ;)

Daniel

  reply	other threads:[~2009-12-18  1:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 20:31 [Buildroot] development environment Marcel
2009-12-17 21:47 ` Peter Korsgaard
2009-12-18  1:10   ` Daniel Mack [this message]
2009-12-18 17:36     ` Marcel
  -- strict thread matches above, loose matches on Subject: below --
2009-01-06 20:08 Aaron Hanson

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=20091218011058.GJ28375@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --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