From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFC: hidden environment variables
Date: Mon, 23 Apr 2007 16:51:43 -0500 [thread overview]
Message-ID: <462D2A6F.5090306@freescale.com> (raw)
In-Reply-To: <1628E43D99629C46988BE46087A3FBB997ACAA@ep-01.EmbeddedPlanet.local>
Jeff Mann wrote:
> You can implement an option that keeps a list of variables that should
> be hidden.
That's dual-maintenance. It would be a lot easier if the environment had support for
generic hidden variables, so I wouldn't need to update that list.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-04-23 21:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 16:46 [U-Boot-Users] RFC: hidden environment variables Timur Tabi
2007-04-23 17:29 ` Grant Likely
2007-04-23 18:47 ` Ulf Samuelsson
2007-04-23 19:22 ` Wolfgang Denk
2007-04-23 20:28 ` Scott Wood
2007-04-23 21:51 ` Wolfgang Denk
2007-04-23 23:20 ` Timur Tabi
2007-04-24 0:12 ` Wolfgang Denk
2007-04-24 18:58 ` Rune Torgersen
2007-04-23 19:28 ` Ben Warren
2007-04-23 19:32 ` Ulf Samuelsson
2007-04-23 19:39 ` Ben Warren
2007-04-23 19:45 ` Timur Tabi
2007-04-23 19:53 ` Ben Warren
2007-04-23 21:49 ` Timur Tabi
2007-04-23 22:04 ` Ben Warren
2007-04-23 21:37 ` Wolfgang Denk
2007-04-23 21:56 ` Timur Tabi
2007-04-23 22:13 ` Wolfgang Denk
2007-04-23 23:19 ` Timur Tabi
2007-04-24 0:06 ` Wolfgang Denk
2007-04-23 21:34 ` Wolfgang Denk
2007-04-24 9:05 ` Ladislav Michl
2007-04-23 19:49 ` Scott Wood
2007-04-23 21:40 ` Wolfgang Denk
2007-04-23 19:50 ` Timur Tabi
2007-04-23 20:05 ` Jeff Mann
2007-04-23 21:46 ` Wolfgang Denk
2007-04-23 21:51 ` Timur Tabi [this message]
2007-04-23 22:05 ` Wolfgang Denk
2007-04-23 23:14 ` Timur Tabi
2007-04-23 23:52 ` Wolfgang Denk
2007-04-24 13:43 ` Truong, Loc
2007-04-23 21:43 ` Wolfgang Denk
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=462D2A6F.5090306@freescale.com \
--to=timur@freescale.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.