From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] i.MX6: mx6qsabrelite: add CONFIG_REVISION_TAG
Date: Sun, 04 Mar 2012 15:41:51 -0700 [thread overview]
Message-ID: <4F53EFAF.5010609@boundarydevices.com> (raw)
In-Reply-To: <20120304220651.E3469202D5E@gemini.denx.de>
On 03/04/2012 03:06 PM, Wolfgang Denk wrote:
> Dear Eric Nelson,
>
> In message<4F53D8E6.4000408@boundarydevices.com> you wrote:
>>
>> Since U-Boot doesn't really have a configuration step, I find that
>> folks tend to tweak the board configuration file quite a bit based
>> on their needs.
>
> Yes, peaople do that a lot, nd it has always been a very good idea to
> at least detect such modifications of the code. The worst thing to
> happen is when you receive a bug report for version FOO, and you have
> no chance of detecting that somebody actually messed with the
> configuration and/or the code.
>
>> Though it's a bit of a hack, we even formalized it on our i.MX5x products
>> to allow customers to keep their git repositories clean:
>> ....
> [Link deleted to not further distribute this horrible stuff.]
>
> Frankly, this "keep their git repositories clean" is a really, really
> bad idea. We pay special care to add the git commit ID to the U-Boot
> version string so you can easily detect if somebody messed with the
> code, and you come up and invent methods of circumventing that.
>
> This is totally counterproductive.
>
> If you use this, that's your business. But please do me the favour and
> do not recommend this to others.
>
We don't. Sorry if I implied otherwise.
We recommend that customers keep their own repositories with changes
from our "standard" releases, but we have a number of customers whose
complete set of differences amounts to default environment variables
and/or choices of serial consoles for which we don't want to carry and
publish an entire configuration.
This hack was borne out of frustration when getting a 'revision-dirty'
reference back from a customer because they've changed something
simple (usually environment settings).
next prev parent reply other threads:[~2012-03-04 22:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 22:55 [U-Boot] i.MX6: mx6qsabrelite: allow use with Freescale 2.6.38 kernels Eric Nelson
2012-03-02 22:55 ` [U-Boot] [PATCH 1/3] i.MX6: mx6qsabrelite: add CONFIG_REVISION_TAG Eric Nelson
2012-03-02 22:59 ` Marek Vasut
2012-03-04 20:35 ` Eric Nelson
2012-03-04 20:59 ` Marek Vasut
2012-03-04 21:04 ` Eric Nelson
2012-03-04 21:18 ` Marek Vasut
2012-03-04 22:06 ` Wolfgang Denk
2012-03-04 22:41 ` Eric Nelson [this message]
2012-03-03 10:26 ` Stefano Babic
2012-03-02 22:55 ` [U-Boot] [PATCH 2/3] i.MX6: mx6qsabrelite: add MACH_TYPE_MX6Q_SABRELITE Eric Nelson
2012-03-02 23:00 ` Marek Vasut
2012-03-03 10:28 ` Stefano Babic
2012-03-02 22:55 ` [U-Boot] [PATCH 3/3] i.MX6: mx6qsabrelite: add ext2 support Eric Nelson
2012-03-07 9:36 ` Stefano Babic
2012-03-02 23:01 ` [U-Boot] i.MX6: mx6qsabrelite: allow use with Freescale 2.6.38 kernels Marek Vasut
2012-03-02 23:25 ` Wolfgang Denk
2012-03-02 23:46 ` Eric Nelson
2012-03-02 23:50 ` Fabio Estevam
2012-03-03 9:33 ` Wolfgang Denk
2012-03-03 6:35 ` Dirk Behme
2012-03-03 9:38 ` Wolfgang Denk
2012-03-03 10:43 ` mailander
2012-03-03 11:32 ` Dirk Behme
2012-03-03 13:30 ` Wolfgang Denk
2012-03-04 1:19 ` Troy Kisky
2012-03-04 8:39 ` Wolfgang Denk
2012-03-07 9:37 ` Albert ARIBAUD
2012-03-04 11:09 ` Stefano Babic
2012-03-04 14:14 ` Igor Grinberg
2012-03-04 19:45 ` [U-Boot] CONFIG_REVISION (was i.MX6: mx6qsabrelite: allow use with Freescale 2.6.38 kernels) Eric Nelson
2012-03-07 8:43 ` Stefano Babic
2012-03-07 15:53 ` Eric Nelson
2012-03-07 16:32 ` Stefano Babic
2012-03-03 10:33 ` [U-Boot] i.MX6: mx6qsabrelite: allow use with Freescale 2.6.38 kernels Stefano Babic
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=4F53EFAF.5010609@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=u-boot@lists.denx.de \
/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.