From: Mike Stump <mikestump@comcast.net>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: David Malcolm <dmalcolm@redhat.com>,
jit@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] update_web_docs_svn: support the JIT docs (PR jit/64257)
Date: Thu, 01 Jan 2015 00:00:00 -0000 [thread overview]
Message-ID: <E5660E2E-91C4-4D33-86D3-3EF9F43077AC@comcast.net> (raw)
In-Reply-To: <alpine.LSU.2.11.1501261235560.2527@tuna.site>
On Jan 26, 2015, at 3:43 AM, Gerald Pfeifer <gerald@pfeifer.com> wrote:
>> +# Again, the jit is a special case, with nested subdirectories
>> +# below "jit", and with some non-HTML files (.png images from us,
>> +# plus .js and .css supplied by sphinx).
>> +for file in $(find jit \
>> + -name "*.html" -o -name "*.css" \
>> + -o -name "*.js" -o -name "*.png"); do
>
> This looks like a Bash-ism. Can you use back ticks
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html
$() is standard and preferred over back ticks. :-) Life goes on.
prev parent reply other threads:[~2015-01-26 18:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:00 David Malcolm
2015-01-01 0:00 ` Gerald Pfeifer
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Jeff Law
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` [PING, www] " David Malcolm
2015-01-01 0:00 ` Gerald Pfeifer
2015-01-01 0:00 ` [PATCH] More fixes for update_web_docs_svn for jit " David Malcolm
2015-01-01 0:00 ` Andrew Pinski
2015-01-01 0:00 ` Gerald Pfeifer
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Gerald Pfeifer
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` [PATCH] maintainer-scripts: Fix 404s in "Show Source" in jit docs David Malcolm
2015-01-01 0:00 ` Gerald Pfeifer
2015-01-01 0:00 ` [PATCH] More fixes for update_web_docs_svn for jit docs (PR jit/64257) David Malcolm
2019-01-01 0:00 ` Gerald Pfeifer
2015-01-01 0:00 ` Mike Stump [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=E5660E2E-91C4-4D33-86D3-3EF9F43077AC@comcast.net \
--to=mikestump@comcast.net \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jit@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).