From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add "source" command; prepare removal of "autoscr" command
Date: Mon, 30 Mar 2009 09:21:28 -0500 [thread overview]
Message-ID: <1238422888.9578.14.camel@localhost.localdomain> (raw)
In-Reply-To: <1238274459-6365-1-git-send-email-wd@denx.de>
The changes look good to me. 2 comments below:
> +/*
> + * Keep for now for backward compatibility;
> + * remove later when support for "autoscr" goes away.
> + */
> +U_BOOT_CMD(
> + autoscr, 2, 0, do_source,
> + "run script from memory",
> + "[addr] - run script starting at addr"
> + " - A valid image header must be present\n"
> +#if defined(CONFIG_FIT)
> + "For FIT format uImage addr must include subimage\n"
> + "unit name in the form of addr:<subimg_uname>\n"
> +#endif
> +);
I'd vote to change autoscr's help messages to something letting end
user's know that the command is deprecated and being replaced by the
"source". Eg something like:
+ autoscr, 2, 0, do_source,
+ "DEPRECATED - see 'source' command",
+ "DEPRECATED - see 'source' command"
Most U-Boot user's are more likely to see this than the
feature-removal-schedule.txt in the source code.
> +#endif
> diff --git a/doc/feature-removal-schedule.txt b/doc/feature-removal-schedule.txt
> index 9ba7a04..cd429a4 100644
> --- a/doc/feature-removal-schedule.txt
> +++ b/doc/feature-removal-schedule.txt
> @@ -8,12 +8,20 @@ file.
> ---------------------------
>
> What: "autoscr" command
> -When: August 2009
> -Why: "autosrc" is an ugly and completely non-standard name. The "autoscr"
> - command is deprecated and will be replaced the "source" command as
> - used by other shells such as bash. Both commands will be supported
> - for a transition period of 6 months after which "autoscr" will be
> - removed.
> +When: Release 2009-09
> +
> +Why: "autosrc" is an ugly and completely non-standard name.
> + The "autoscr" command is deprecated and will be replaced by
> +
There's an out of place newline here.
> + the "source" command as used by other shells such as bash.
> +
> + Starting with March 2009, both commands will be supported for
> + a transition period of 6 months after which "autoscr" will be
> + removed. During the transition period existing scripts and
> + environment variable names remain untouched for maximum
> + compatibiltiy; thse will be changed when support for the
> + "autoscr" command get's finally dropped.
s/compatibiltiy/compatibility/ s/thse/these/ and s/get's finally/finally
gets/
Best,
Peter
next prev parent reply other threads:[~2009-03-30 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 21:07 [U-Boot] [PATCH] Add "source" command; prepare removal of "autoscr" command Wolfgang Denk
2009-03-30 14:21 ` Peter Tyser [this message]
2009-03-31 9:37 ` Detlev Zundel
2009-03-31 10:31 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2009-04-01 21:34 Wolfgang Denk
2009-04-03 20:02 ` 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=1238422888.9578.14.camel@localhost.localdomain \
--to=ptyser@xes-inc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox