From: "Carsey, Jaben" <jaben.carsey@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
Vladimir Olovyannikov <vladimir.olovyannikov@broadcom.com>
Cc: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>,
"Carsey, Jaben" <jaben.carsey@intel.com>
Subject: Re: [PATCH] GPT Shell Application/Library
Date: Mon, 17 Oct 2016 16:35:43 +0000 [thread overview]
Message-ID: <CB6E33457884FA40993F35157061515C54A90E8E@FMSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <54ded7fa-1f35-1bf9-b5e6-d78f2984bf86@redhat.com>
Laszlo,
We don't have a hard and fast rule about command names. The simple thing is that we may have a conflict in the future, but I don't see that as likely at this point.
Your comment about _ was when a custom implementation wants to extend an existing defined command with a non-standard parameter. For example there is an _exit parameter to the shell that tells the shell to auto-close after running the initial command line passed into it.
-Jaben
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Laszlo Ersek
> Sent: Monday, October 17, 2016 2:44 AM
> To: Vladimir Olovyannikov <vladimir.olovyannikov@broadcom.com>
> Cc: Carsey, Jaben <jaben.carsey@intel.com>; Ni, Ruiyu
> <ruiyu.ni@intel.com>; edk2-devel@lists.01.org <edk2-devel@ml01.01.org>
> Subject: Re: [edk2] [PATCH] GPT Shell Application/Library
> Importance: High
>
> On 10/17/16 08:49, Vladimir Olovyannikov wrote:
> > Thank you Laszlo,
> >
> > Sorry, I missed the fields; it is my first contribution, I will add the
> > required lines, review the source according to your comments and will
> > resubmit the patch.
> > So do you think the command should be _gpt instead of gpt? I was
> > following TFTP and SF commands as a template.
>
> Right, at this point I'm confused about TFTP even, in retrospect. It's
> not in the spec, so I guess it should have been _TFTP. I hope Jaben and
> Ray can advise us. :)
>
> Thanks
> Laszlo
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2016-10-17 16:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 5:23 [PATCH] GPT Shell Application/Library Vladimir Olovyannikov
2016-10-16 20:05 ` Laszlo Ersek
[not found] ` <CACmgjazi_K4Qo5=TeO_tCGK2cB26d0rqOEZh6TthP1UYbo6J6w@mail.gmail.com>
[not found] ` <CACmgjaziUEF2EsSn73HY5JvL2rmRWrXS+rHMtOQ1HaRwPpXS+g@mail.gmail.com>
2016-10-17 6:49 ` Vladimir Olovyannikov
2016-10-17 7:24 ` Michael Zimmermann
2016-10-17 17:52 ` Vladimir Olovyannikov
2016-10-17 17:56 ` Carsey, Jaben
2016-10-18 13:59 ` Shah, Tapan
2016-10-18 16:58 ` Vladimir Olovyannikov
2016-10-18 17:04 ` Carsey, Jaben
2016-10-18 18:03 ` Shah, Tapan
2016-10-18 19:09 ` Vladimir Olovyannikov
2016-10-18 17:23 ` Laszlo Ersek
2016-10-18 18:03 ` Vladimir Olovyannikov
2016-10-18 18:12 ` Laszlo Ersek
2016-10-17 9:43 ` Laszlo Ersek
2016-10-17 16:35 ` Carsey, Jaben [this message]
2016-10-18 1:45 ` Ni, Ruiyu
2016-10-18 1:48 ` Tim Lewis
2016-10-18 1:55 ` Ni, Ruiyu
2016-10-18 2:59 ` Carsey, Jaben
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-list 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=CB6E33457884FA40993F35157061515C54A90E8E@FMSMSX103.amr.corp.intel.com \
--to=devel@edk2.groups.io \
/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