Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] B2_EXTERNAL and patches
Date: Fri, 12 Dec 2014 10:11:52 +0100 (CET)	[thread overview]
Message-ID: <2020988860.29161610.1418375512251.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <trinity-73676462-8b93-436d-9361-468b01882a1f-1418374738886@3capp-gmx-bs63>

you might want to look at https://github.com/Openwide-Ingenierie/buildroot-submodule which is meant to solve that sort of problems.

each variant will share the patch directroy by default, but you can override that on a per-variant basis

Cordialement 

J?r?my Rosen 
+33 (0)1 42 68 28 04

fight key loggers : write some perl using vim 


Open Wide Ingenierie

23, rue Daviel
75013 Paris - France
www.openwide.fr





----- Mail original -----
> I would like use one minimal patched Builroot release in one branch
> for multiple projects,
> so is it also possible to maintain different patches for a packages
> in different external folders?
> Or could the selecition of patches be controlled by a configuration
> file?
> (the different pachtes are necessary because of differenr kernel
> versions)
> 
> Peter
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>

      parent reply	other threads:[~2014-12-12  9:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12  8:58 [Buildroot] B2_EXTERNAL and patches Peter Kuemmel
2014-12-12  9:06 ` Thomas Petazzoni
2014-12-12  9:15   ` Peter Kümmel
2014-12-12  9:11 ` Jeremy Rosen [this message]

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=2020988860.29161610.1418375512251.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox