From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] barebox: add custom version option
Date: Wed, 1 May 2013 23:10:09 +0200 [thread overview]
Message-ID: <20130501231009.787484f5@skate> (raw)
In-Reply-To: <1366184503-16875-2-git-send-email-fabio.porcedda@gmail.com>
Dear Fabio Porcedda,
On Wed, 17 Apr 2013 09:41:41 +0200, Fabio Porcedda wrote:
> -config BR2_TARGET_BAREBOX_2013_01
> - bool "2013.01.0"
> -
> -config BR2_TARGET_BAREBOX_2013_02
> - bool "2013.02.0"
> -
> -config BR2_TARGET_BAREBOX_2013_03
> - bool "2013.03.0"
> -
> -config BR2_TARGET_BAREBOX_2013_04
> +config BR2_TARGET_BAREBOX_LATEST_VERSION
> bool "2013.04.0"
>
> +config BR2_TARGET_BAREBOX_CUSTOM_VERSION
> + bool "Custom version"
> + help
> + This option allows to use a specific official versions
> +
We need to have something that is consistent between U-Boot, Barebox
and the kernel. Currently U-Boot has a version selection, the Linux
kernel allows to chose the latest version (but with an option named
after the version itself, so the name of the option changes when the
version changes) or a custom version, and now for Barebox you're
proposing yet another solution: select the latest version (with an
option name that never changes) or a custom version.
So, I'm fine doing changes on this, but they should be consistent
across packages.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-05-01 21:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 7:41 [Buildroot] [PATCH v2 0/3] barebox new option and new boards Fabio Porcedda
2013-04-17 7:41 ` [Buildroot] [PATCH v2 1/3] barebox: add custom version option Fabio Porcedda
2013-05-01 21:10 ` Thomas Petazzoni [this message]
2013-05-03 6:49 ` Fabio Porcedda
2013-05-03 7:57 ` Fabio Porcedda
2013-05-03 8:55 ` Thomas Petazzoni
2013-05-03 9:17 ` Fabio Porcedda
2013-05-03 10:11 ` Thomas Petazzoni
2013-05-03 16:46 ` Arnout Vandecappelle
2013-05-06 14:15 ` Peter Korsgaard
2013-05-03 10:50 ` Peter Korsgaard
2013-05-03 11:26 ` Fabio Porcedda
2013-04-17 7:41 ` [Buildroot] [PATCH v2 2/3] configs: add defconfig for Telit EVK-PRO3 Fabio Porcedda
2013-05-01 21:13 ` Thomas Petazzoni
2013-05-01 22:14 ` Fabio Porcedda
2013-05-02 9:58 ` Thomas Petazzoni
2013-04-17 7:41 ` [Buildroot] [PATCH v2 3/3] configs: add defconfig for Atmel AT91SAM9260-EK Nand Flash Boot Fabio Porcedda
2013-05-01 21:14 ` Thomas Petazzoni
2013-05-01 22:04 ` Fabio Porcedda
2013-05-02 9:59 ` Thomas Petazzoni
2013-05-01 6:57 ` [Buildroot] [PATCH v2 0/3] barebox new option and new boards Fabio Porcedda
2013-05-03 8:24 ` Fabio Porcedda
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=20130501231009.787484f5@skate \
--to=thomas.petazzoni@free-electrons.com \
--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