All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] change default location for local.mk to $(CONFIG_DIR)
Date: Tue, 12 Mar 2013 09:12:12 +0100 (CET)	[thread overview]
Message-ID: <1706669320.395518.1363075932486.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <20130311222630.5a75029d@skate>

> Dear J?r?my Rosen,
> 
> On Thu,  7 Mar 2013 11:49:23 +0100, J?r?my Rosen wrote:
> > the previous default of $(TOPDIR) broke the philosophy of builds
> > with O=
> > which try to keep all configuration files within the $(CONFIG_DIR)
> > subtree
> 
> Hum, that's an interesting vision of things. I think I would tend to
> agree with this idea.
> 
> What do others think?
> 

A bit of context : 

I am trying to keep my buildroot project in git, but I am trying to 
cleanly separate "changes made to git" and "changes due to my project.

that basically means that all config file needs to be out of the 
buildroot/ subdirectory to be able to easily generate patches against
mainline and still keep my changes in git. I do that using git-subtree

I also change the location of the kernel config file for the same reason
and would do that for ctng and busybox if I needed to change them from
their default config

    Regards

    J?r?my Rosen

fight key loggers : write some perl using vim

  reply	other threads:[~2013-03-12  8:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 10:49 [Buildroot] [PATCH] change default location for local.mk to $(CONFIG_DIR) Jérémy Rosen
2013-03-11 21:26 ` Thomas Petazzoni
2013-03-12  8:12   ` Jeremy Rosen [this message]
2013-03-12 21:47     ` Arnout Vandecappelle
2013-03-14  8:37       ` Jeremy Rosen
2013-03-18  6:46         ` Arnout Vandecappelle
2013-03-18  8:10           ` Jeremy Rosen
2013-03-12  8:26   ` Thomas De Schampheleire
2013-03-15 11:46     ` Thomas Petazzoni

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=1706669320.395518.1363075932486.JavaMail.root@openwide.fr \
    --to=jeremy.rosen@openwide.fr \
    --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 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.