From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Standardize bootp, tftpboot, rarpboot, dhcp, and nfs command descriptions
Date: Tue, 26 Aug 2008 12:16:18 -0500 [thread overview]
Message-ID: <1219770978.11226.34.camel@localhost.localdomain> (raw)
In-Reply-To: <48B42FD9.1080909@gmail.com>
Hi Ben,
On Tue, 2008-08-26 at 09:31 -0700, Ben Warren wrote:
> Hi Peter,
>
> Peter Tyser wrote:
> > cmd_net.c command descriptions were updated to describe the optional
> > hostIPaddr argument. The dhcp command help message was also updated
> > to more closely reflect the other commands in cmd_net.c
> >
> > Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
> > ---
> >
> I'm too lazy to check if this is different from the patch that you sent
> previously (8/13 or so). I imagine you want this one applied and the
> other discarded?
The content of this patch is identical to the previous patch sent on
8/13. However, the email on 8/13's title included "[RFC]" and in it I
made the following comment:
"Not sure if "boot" is the proper word to use in the command definitions
since the downloaded images are only booted if "autostart=yes", and
the majority of board configs don't have autostart set to yes.
I'd vote for changing the descriptions to "load image via...".
If a new, more granular bootm command is in the works,
it seems like even less people will autoboot an image
directly before doing some additional bootm commands to prep
for booting an OS. Do others have an opinion?"
No one seemed to bite as far as changing the wording of the commands, so
I re-sent the same patch without the [RFC] and cleaned up the commit
message to make it a formal patch. So you're right, this patch should
be applied and the previous one on 8/13 discarded.
Thanks,
Peter
next prev parent reply other threads:[~2008-08-26 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 16:17 [U-Boot] [PATCH] Standardize bootp, tftpboot, rarpboot, dhcp, and nfs command descriptions Peter Tyser
2008-08-26 16:31 ` Ben Warren
2008-08-26 17:16 ` Peter Tyser [this message]
2008-08-26 20:30 ` Ben Warren
2008-08-27 5:46 ` Ben Warren
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=1219770978.11226.34.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