public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Carsey, Jaben" <jaben.carsey@intel.com>
To: Jeff Westfahl <jeff.westfahl@ni.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Ni, Ruiyu" <ruiyu.ni@intel.com>
Subject: Re: Shell 'touch' command fails if touched file doesn't already exist
Date: Sun, 14 May 2017 22:13:07 +0000	[thread overview]
Message-ID: <CB6E33457884FA40993F35157061515C630BCC9B@FMSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1705121640230.14493@jmw-lm181>

I think that since the UEFI Shell Spec does not mention creating new files and no one has mentioned it before, we just didn't think of it.  I don't see that it would violate the spec; I would welcome such a enhancement.

-Jaben

> -----Original Message-----
> From: Jeff Westfahl [mailto:jeff.westfahl@ni.com]
> Sent: Friday, May 12, 2017 2:44 PM
> To: edk2-devel@lists.01.org
> Cc: Ni, Ruiyu <ruiyu.ni@intel.com>; Carsey, Jaben <jaben.carsey@intel.com>
> Subject: Shell 'touch' command fails if touched file doesn't already exist
> Importance: High
> 
> I see that the shell 'touch' command doesn't create the specified file if it doesn't
> already exist. Is this by design? My experience with the 'touch' command in
> other operating environments leads me to expect it to create the file if it doesn't
> already exist.
> 
> Regards,
> Jeff


      reply	other threads:[~2017-05-14 22:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12 21:43 Shell 'touch' command fails if touched file doesn't already exist Jeff Westfahl
2017-05-14 22:13 ` Carsey, Jaben [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-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=CB6E33457884FA40993F35157061515C630BCC9B@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