From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] CONFIG naming convetion
Date: Sat, 18 Jul 2009 21:08:33 +0200 [thread overview]
Message-ID: <20090718190833.B6CD7832E416@gemini.denx.de> (raw)
In-Reply-To: <200907181456.20670.vapier@gentoo.org>
Dear Mike Frysinger,
In message <200907181456.20670.vapier@gentoo.org> you wrote:
>
> are there really any guidelines on what "CONFIG_SYS_" is for ? i havent
> really figured out what "_SYS_" is supposed to indicate, so the new proposed
> naming is just as confusing imo.
Actually there ARE guidelines; they are not perfect, but better than
nothing.
It helps to read the README.
If you think this is insufficint and yoiu have better ideas, please
post a patch.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The price of curiosity is a terminal experience.
- Terry Pratchett, _The Dark Side of the Sun_
prev parent reply other threads:[~2009-07-18 19:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 11:03 [U-Boot] [RFC] CONFIG naming convetion Jean-Christophe PLAGNIOL-VILLARD
2009-07-18 12:50 ` Wolfgang Denk
2009-07-18 13:05 ` Heiko Schocher
2009-07-18 14:48 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-18 17:33 ` Wolfgang Denk
2009-07-18 15:15 ` Robin Getz
2009-07-18 15:52 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-18 21:30 ` Robin Getz
2009-07-18 17:50 ` Wolfgang Denk
2009-07-18 21:13 ` Robin Getz
2009-07-18 22:25 ` Wolfgang Denk
2009-07-20 3:55 ` Robin Getz
2009-07-20 20:33 ` Wolfgang Denk
2009-07-21 15:59 ` Robin Getz
2009-07-20 8:02 ` Alessandro Rubini
2009-07-20 14:27 ` Wolfgang Denk
2009-07-19 5:54 ` Heiko Schocher
2009-07-18 18:56 ` Mike Frysinger
2009-07-18 19:08 ` Wolfgang Denk [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=20090718190833.B6CD7832E416@gemini.denx.de \
--to=wd@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox