From: Elia Pinto <gitter.spiros@gmail.com>
To: git@vger.kernel.org
Cc: Elia Pinto <gitter.spiros@gmail.com>
Subject: [PATCH 00/12] use the $( ... ) construct for command substitution
Date: Tue, 12 Jan 2016 11:49:26 +0000 [thread overview]
Message-ID: <1452599378-47882-1-git-send-email-gitter.spiros@gmail.com> (raw)
This patch series continues the changes introduced with the merge
6753d8a85d543253d95184ec2faad6dc197f248:
Merge branch 'ep/shell-command-substitution'
Adjust shell scripts to use $(cmd) instead of `cmd`.
This is the is the ninth and final series.
*** BLURB HERE ***
Elia Pinto (12):
t9119-git-svn-info.sh: use the $( ... ) construct for command
substitution
t9129-git-svn-i18n-commitencoding.sh: use the $( ... ) construct for
command substitution
t9130-git-svn-authors-file.sh: use the $( ... ) construct for command
substitution
t9132-git-svn-broken-symlink.sh: use the $( ... ) construct for
command substitution
t9137-git-svn-dcommit-clobber-series.sh: use the $( ... ) construct
for command substitution
t9138-git-svn-authors-prog.sh: use the $( ... ) construct for command
substitution
t9145-git-svn-master-branch.sh: use the $( ... ) construct for command
substitution
t9150-svk-mergetickets.sh: use the $( ... ) construct for command
substitution
t9300-fast-import.sh: use the $( ... ) construct for command
substitution
t9350-fast-export.sh: use the $( ... ) construct for command
substitution
t9501-gitweb-standalone-http-status.sh: use the $( ... ) construct for
command substitution
t9901-git-web--browse.sh: use the $( ... ) construct for command
substitution
t/t9119-git-svn-info.sh | 2 +-
t/t9129-git-svn-i18n-commitencoding.sh | 4 +-
t/t9130-git-svn-authors-file.sh | 12 +++---
t/t9132-git-svn-broken-symlink.sh | 4 +-
t/t9137-git-svn-dcommit-clobber-series.sh | 24 +++++------
t/t9138-git-svn-authors-prog.sh | 2 +-
t/t9145-git-svn-master-branch.sh | 4 +-
t/t9150-svk-mergetickets.sh | 2 +-
t/t9300-fast-import.sh | 68 +++++++++++++++----------------
t/t9350-fast-export.sh | 6 +--
t/t9501-gitweb-standalone-http-status.sh | 6 +--
t/t9901-git-web--browse.sh | 2 +-
12 files changed, 68 insertions(+), 68 deletions(-)
--
2.5.0
next reply other threads:[~2016-01-12 11:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 11:49 Elia Pinto [this message]
2016-01-12 11:49 ` [PATCH 01/12] t9119-git-svn-info.sh: use the $( ... ) construct for command substitution Elia Pinto
2016-01-12 11:49 ` [PATCH 02/12] t9129-git-svn-i18n-commitencoding.sh: " Elia Pinto
2016-01-12 11:49 ` [PATCH 03/12] t9130-git-svn-authors-file.sh: " Elia Pinto
2016-01-12 11:49 ` [PATCH 04/12] t9132-git-svn-broken-symlink.sh: " Elia Pinto
2016-01-12 11:49 ` [PATCH 05/12] t9137-git-svn-dcommit-clobber-series.sh: " Elia Pinto
2016-01-12 11:49 ` [PATCH 06/12] t9138-git-svn-authors-prog.sh: " Elia Pinto
2016-01-12 11:49 ` [PATCH 07/12] t9145-git-svn-master-branch.sh: " Elia Pinto
2016-01-12 11:49 ` [PATCH 08/12] t9150-svk-mergetickets.sh: " Elia Pinto
2016-01-12 19:59 ` Junio C Hamano
2016-01-12 11:49 ` [PATCH 09/12] t9300-fast-import.sh: " Elia Pinto
2016-01-12 11:49 ` [PATCH 10/12] t9350-fast-export.sh: " Elia Pinto
2016-01-12 11:49 ` [PATCH 11/12] t9501-gitweb-standalone-http-status.sh: " Elia Pinto
2016-01-12 11:49 ` [PATCH 12/12] t9901-git-web--browse.sh: " Elia Pinto
2016-01-12 19:51 ` [PATCH 00/12] " Junio C Hamano
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=1452599378-47882-1-git-send-email-gitter.spiros@gmail.com \
--to=gitter.spiros@gmail.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).