From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] blank line repeats last command
Date: Fri, 23 Oct 2009 13:59:30 -0500 [thread overview]
Message-ID: <4AE1FD12.7080604@freescale.com> (raw)
In-Reply-To: <1ba63b520910231148r24112dc5m36556f5c9dd16314@mail.gmail.com>
Frank Svendsb?e wrote:
> I partly agree with David Collier on this matter. Before I discovered
> this was a feature,
> I was sure this was a bug, but I understand some of you reasoning..
> just not all. For instance,
> I can understand why it's handy when dumping memory, but what's the
> rationale behind
> having 'cp.b' repeating? It's annoying when writing large files to
> slow (NOR) flash.
Indeed it is.
IMHO, rather than select a few "dangerous" commands to exempt from autorepeat,
it should be off for most commands and selectively enabled for a handful of
commands where it's really useful (such as autoincrement dumps).
-Scott
next prev parent reply other threads:[~2009-10-23 18:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 10:56 [U-Boot] blank line repeats last command David Collier
2009-10-23 11:26 ` Jerry Van Baren
2009-10-23 11:49 ` David Collier
2009-10-23 11:55 ` Jerry Van Baren
2009-10-23 18:48 ` Frank Svendsbøe
2009-10-23 18:59 ` Scott Wood [this message]
2009-10-23 19:27 ` Peter Tyser
2009-10-23 13:46 ` 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=4AE1FD12.7080604@freescale.com \
--to=scottwood@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox