All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaap de Jong <jaap.dejong@nedap.com>
To: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: best practice for different projects on the same board
Date: Fri, 25 Jan 2013 12:19:09 +0100	[thread overview]
Message-ID: <51026A2D.1030705@nedap.com> (raw)

Hi All,
I'm wondering what the best practice would be in the following situation.
We have a board that is going to be used in several projects.
The set of basic packages is the same but every project might have some 
minor and perhaps sometimes major differences in f.i. config files.
I don't want to make a copy of the base project for every upcoming new 
project. I would really like to handle with the differences only.
What is the best approach for this?
Thanks!
Jaap




             reply	other threads:[~2013-01-25 11:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25 11:19 Jaap de Jong [this message]
2013-01-25 11:40 ` best practice for different projects on the same board Marcin Juszkiewicz

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=51026A2D.1030705@nedap.com \
    --to=jaap.dejong@nedap.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.