From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Change the visible output for transfers to display hex numbers
Date: Tue, 25 Jan 2011 11:49:20 +0100 [thread overview]
Message-ID: <4D3EAAB0.8090103@ahsoftware.de> (raw)
In-Reply-To: <20110125102743.B8343BB0B9@gemini.denx.de>
Hello,
Am 25.01.2011 11:27, schrieb Wolfgang Denk:
> Dear Alexander Holler,
>
> In message<1295950537-12363-1-git-send-email-holler@ahsoftware.de> you wrote:
>> When files were transfered the output is currently
>> -
>> Bytes transferred = 1976384 (1e2840 hex)
>> -
>> Using the decimal length as input for other commands conflicts with the
>> the default base of 16 needed.
>>
>> Change the output to
>> -
>> Bytes transferred = 0x1e2840 (1976384 bytes)
>> -
>> to reflect what should be used as input for other commands.
>
> In which way does this reflect what "should be used as input for other
> commands"?
>
> I don't even understand why you use this manually with copy& paste.
>
> Why don't you simply refer to the ${filesize} variable?
TIMTOWTDI
> In any case, if you want to change this format, you must change _all_
> occurrences of it, i. e. include all the commands that load from
> external storage (ide, usb, scsi, sata, nand, dataflash, SPI-Flash,
> ...).
Than I prefer not to change something and live with that
unorthogonality. Besides several READMEs, net/net.c is the only source where
git grep "Bytes transferred"
shows that such an output is used.
Regards,
Alexander
prev parent reply other threads:[~2011-01-25 10:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 10:15 [U-Boot] [PATCH] Change the visible output for transfers to display hex numbers Alexander Holler
2011-01-25 10:27 ` Wolfgang Denk
2011-01-25 10:49 ` Alexander Holler [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=4D3EAAB0.8090103@ahsoftware.de \
--to=holler@ahsoftware.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