This patch series changes everywhere the back-quotes construct for command
substitution with the $( ... ). The Git CodingGuidelines prefer
the $( ... ) construct for command substitution instead of using the back-quotes
, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell. Because this construct uses distinct
opening and closing delimiters, it is much easier to follow.
Also now the embedded double quotes no longer need escaping.
The patch is simple but involves a large number of files with different authors.
Being simple I think it is wasteful to cc a large number of different people
for doing a review.
This is a second reroll after the
Matthieu Moy review. Changes from v1:
- Dropped the silly patches to t6111-rev-list-treesame.sh,
t0204-gettext-reencode-sanity.sh.
- Simple reformatting of the commit message.
- added the toy script used for doing the patch.
Elia Pinto (142):
check-builtins.sh: use the $( ... ) construct for command
substitution
git-am.sh: use the $( ... ) construct for command substitution
git-pull.sh: use the $( ... ) construct for command substitution
git-rebase--merge.sh: use the $( ... ) construct for command
substitution
git-rebase.sh: use the $( ... ) construct for command substitution
git-stash.sh: use the $( ... ) construct for command substitution
git-web--browse.sh: use the $( ... ) construct for command
substitution
unimplemented.sh: use the $( ... ) construct for command substitution
t0001-init.sh: use the $( ... ) construct for command substitution
t0010-racy-git.sh: use the $( ... ) construct for command
substitution
t0020-crlf.sh: use the $( ... ) construct for command substitution
t0025-crlf-auto.sh: use the $( ... ) construct for command
substitution
t0026-eol-config.sh: use the $( ... ) construct for command
substitution
t0030-stripspace.sh: use the $( ... ) construct for command
substitution
t0300-credentials.sh: use the $( ... ) construct for command
substitution
t1000-read-tree-m-3way.sh: use the $( ... ) construct for command
substitution
t1001-read-tree-m-2way.sh: use the $( ... ) construct for command
substitution
t1002-read-tree-m-u-2way.sh: use the $( ... ) construct for command
substitution
t1003-read-tree-prefix.sh: use the $( ... ) construct for command
substitution
t1004-read-tree-m-u-wf.sh: use the $( ... ) construct for command
substitution
t1020-subdirectory.sh: use the $( ... ) construct for command
substitution
t1050-large.sh: use the $( ... ) construct for command substitution
t1100-commit-tree-options.sh: use the $( ... ) construct for command
substitution
t1401-symbolic-ref.sh: use the $( ... ) construct for command
substitution
t1410-reflog.sh: use the $( ... ) construct for command substitution
t1511-rev-parse-caret.sh: use the $( ... ) construct for command
substitution
t1512-rev-parse-disambiguation.sh: use the $( ... ) construct for
command substitution
t2102-update-index-symlinks.sh: use the $( ... ) construct for
command substitution
t3030-merge-recursive.sh: use the $( ... ) construct for command
substitution
t3100-ls-tree-restrict.sh: use the $( ... ) construct for command
substitution
t3101-ls-tree-dirname.sh: use the $( ... ) construct for command
substitution
t3210-pack-refs.sh: use the $( ... ) construct for command
substitution
t3403-rebase-skip.sh: use the $( ... ) construct for command
substitution
t3511-cherry-pick-x.sh: use the $( ... ) construct for command
substitution
t3600-rm.sh: use the $( ... ) construct for command substitution
t3700-add.sh: use the $( ... ) construct for command substitution
t3905-stash-include-untracked.sh: use the $( ... ) construct for
command substitution
t3910-mac-os-precompose.sh: use the $( ... ) construct for command
substitution
t4006-diff-mode.sh: use the $( ... ) construct for command
substitution
t4010-diff-pathspec.sh: use the $( ... ) construct for command
substitution
t4012-diff-binary.sh: use the $( ... ) construct for command
substitution
t4013-diff-various.sh: use the $( ... ) construct for command
substitution
t4014-format-patch.sh: use the $( ... ) construct for command
substitution
t4036-format-patch-signer-mime.sh: use the $( ... ) construct for
command substitution
t4038-diff-combined.sh: use the $( ... ) construct for command
substitution
t4057-diff-combined-paths.sh: use the $( ... ) construct for command
substitution
t4116-apply-reverse.sh: use the $( ... ) construct for command
substitution
t4119-apply-config.sh: use the $( ... ) construct for command
substitution
t4204-patch-id.sh: use the $( ... ) construct for command
substitution
t5000-tar-tree.sh: use the $( ... ) construct for command
substitution
t5003-archive-zip.sh: use the $( ... ) construct for command
substitution
t5100-mailinfo.sh: use the $( ... ) construct for command
substitution
t5300-pack-object.sh: use the $( ... ) construct for command
substitution
t5301-sliding-window.sh: use the $( ... ) construct for command
substitution
t5302-pack-index.sh: use the $( ... ) construct for command
substitution
t5303-pack-corruption-resilience.sh: use the $( ... ) construct for
command substitution
t5304-prune.sh: use the $( ... ) construct for command substitution
t5305-include-tag.sh: use the $( ... ) construct for command
substitution
t5500-fetch-pack.sh: use the $( ... ) construct for command
substitution
t5505-remote.sh: use the $( ... ) construct for command substitution
t5506-remote-groups.sh: use the $( ... ) construct for command
substitution
t5510-fetch.sh: use the $( ... ) construct for command substitution
t5515-fetch-merge-logic.sh: use the $( ... ) construct for command
substitution
t5516-fetch-push.sh: use the $( ... ) construct for command
substitution
t5517-push-mirror.sh: use the $( ... ) construct for command
substitution
t5520-pull.sh: use the $( ... ) construct for command substitution
t5522-pull-symlink.sh: use the $( ... ) construct for command
substitution
t5530-upload-pack-error.sh: use the $( ... ) construct for command
substitution
t5537-fetch-shallow.sh: use the $( ... ) construct for command
substitution
t5538-push-shallow.sh: use the $( ... ) construct for command
substitution
t5550-http-fetch-dumb.sh: use the $( ... ) construct for command
substitution
t5551-http-fetch-smart.sh: use the $( ... ) construct for command
substitution
t5570-git-daemon.sh: use the $( ... ) construct for command
substitution
t5601-clone.sh: use the $( ... ) construct for command substitution
t5700-clone-reference.sh: use the $( ... ) construct for command
substitution
t5710-info-alternate.sh: use the $( ... ) construct for command
substitution
t5900-repo-selection.sh: use the $( ... ) construct for command
substitution
t6001-rev-list-graft.sh: use the $( ... ) construct for command
substitution
t6002-rev-list-bisect.sh: use the $( ... ) construct for command
substitution
t6015-rev-list-show-all-parents.sh: use the $( ... ) construct for
command substitution
t6032-merge-large-rename.sh: use the $( ... ) construct for command
substitution
t6034-merge-rename-nocruft.sh: use the $( ... ) construct for command
substitution
t6132-pathspec-exclude.sh: use the $( ... ) construct for command
substitution
t7001-mv.sh: use the $( ... ) construct for command substitution
t7003-filter-branch.sh: use the $( ... ) construct for command
substitution
t7004-tag.sh: use the $( ... ) construct for command substitution
t7006-pager.sh: use the $( ... ) construct for command substitution
t7103-reset-bare.sh: use the $( ... ) construct for command
substitution
t7406-submodule-update.sh: use the $( ... ) construct for command
substitution
t7408-submodule-reference.sh: use the $( ... ) construct for command
substitution
t7504-commit-msg-hook.sh: use the $( ... ) construct for command
substitution
t7505-prepare-commit-msg-hook.sh: use the $( ... ) construct for
command substitution
t7602-merge-octopus-many.sh: use the $( ... ) construct for command
substitution
t7700-repack.sh: use the $( ... ) construct for command substitution
t8003-blame-corner-cases.sh: use the $( ... ) construct for command
substitution
t9001-send-email.sh: use the $( ... ) construct for command
substitution
t9101-git-svn-props.sh: use the $( ... ) construct for command
substitution
t9104-git-svn-follow-parent.sh: use the $( ... ) construct for
command substitution
t9105-git-svn-commit-diff.sh: use the $( ... ) construct for command
substitution
t9107-git-svn-migrate.sh: use the $( ... ) construct for command
substitution
t9108-git-svn-glob.sh: use the $( ... ) construct for command
substitution
t9109-git-svn-multi-glob.sh: use the $( ... ) construct for command
substitution
t9110-git-svn-use-svm-props.sh: use the $( ... ) construct for
command substitution
t9114-git-svn-dcommit-merge.sh: use the $( ... ) construct for
command substitution
t9118-git-svn-funky-branch-names.sh: use the $( ... ) construct for
command substitution
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
test-lib-functions.sh: use the $( ... ) construct for command
substitution
lib-credential.sh: use the $( ... ) construct for command
substitution
lib-cvs.sh: use the $( ... ) construct for command substitution
lib-gpg.sh: use the $( ... ) construct for command substitution
p5302-pack-index.sh: use the $( ... ) construct for command
substitution
howto-index.sh: use the $( ... ) construct for command substitution
install-webdoc.sh: use the $( ... ) construct for command
substitution
git-checkout.sh: use the $( ... ) construct for command substitution
git-clone.sh: use the $( ... ) construct for command substitution
git-commit.sh: use the $( ... ) construct for command substitution
git-fetch.sh: use the $( ... ) construct for command substitution
git-ls-remote.sh: use the $( ... ) construct for command substitution
git-merge.sh: use the $( ... ) construct for command substitution
git-repack.sh: use the $( ... ) construct for command substitution
git-resolve.sh: use the $( ... ) construct for command substitution
git-revert.sh: use the $( ... ) construct for command substitution
git-tag.sh: use the $( ... ) construct for command substitution
t9360-mw-to-git-clone.sh: use the $( ... ) construct for command
substitution
t9362-mw-to-git-utf8.sh: use the $( ... ) construct for command
substitution
t9365-continuing-queries.sh: use the $( ... ) construct for command
substitution
test-gitmw-lib.sh: use the $( ... ) construct for command
substitution
t7900-subtree.sh: use the $( ... ) construct for command substitution
appp.sh: use the $( ... ) construct for command substitution
txt-to-pot.sh: use the $( ... ) construct for command substitution
t9100-git-svn-basic.sh: use the $( ... ) construct for command
substitution
Documentation/howto-index.sh | 12 ++--
Documentation/install-webdoc.sh | 6 +-
check-builtins.sh | 4 +-
contrib/examples/git-checkout.sh | 8 +--
contrib/examples/git-clone.sh | 20 +++----
contrib/examples/git-commit.sh | 10 ++--
contrib/examples/git-fetch.sh | 6 +-
contrib/examples/git-ls-remote.sh | 4 +-
contrib/examples/git-merge.sh | 4 +-
contrib/examples/git-repack.sh | 2 +-
contrib/examples/git-resolve.sh | 2 +-
contrib/examples/git-revert.sh | 2 +-
contrib/examples/git-tag.sh | 2 +-
contrib/mw-to-git/t/t9360-mw-to-git-clone.sh | 14 ++---
contrib/mw-to-git/t/t9362-mw-to-git-utf8.sh | 4 +-
contrib/mw-to-git/t/t9365-continuing-queries.sh | 2 +-
contrib/mw-to-git/t/test-gitmw-lib.sh | 6 +-
contrib/subtree/t/t7900-subtree.sh | 2 +-
contrib/thunderbird-patch-inline/appp.sh | 14 ++---
git-am.sh | 30 +++++-----
git-gui/po/glossary/txt-to-pot.sh | 4 +-
git-pull.sh | 2 +-
git-rebase--merge.sh | 4 +-
git-rebase.sh | 8 +--
git-stash.sh | 2 +-
git-web--browse.sh | 6 +-
t/lib-credential.sh | 2 +-
t/lib-cvs.sh | 2 +-
t/lib-gpg.sh | 2 +-
t/perf/p5302-pack-index.sh | 2 +-
t/t0001-init.sh | 12 ++--
t/t0010-racy-git.sh | 4 +-
t/t0020-crlf.sh | 42 +++++++-------
t/t0025-crlf-auto.sh | 38 ++++++-------
t/t0026-eol-config.sh | 20 +++----
t/t0030-stripspace.sh | 20 +++----
t/t0300-credentials.sh | 2 +-
t/t1000-read-tree-m-3way.sh | 4 +-
t/t1001-read-tree-m-2way.sh | 18 +++---
t/t1002-read-tree-m-u-2way.sh | 10 ++--
t/t1003-read-tree-prefix.sh | 2 +-
t/t1004-read-tree-m-u-wf.sh | 8 +--
t/t1020-subdirectory.sh | 22 ++++----
t/t1050-large.sh | 4 +-
t/t1100-commit-tree-options.sh | 4 +-
t/t1401-symbolic-ref.sh | 2 +-
t/t1410-reflog.sh | 24 ++++----
t/t1511-rev-parse-caret.sh | 4 +-
t/t1512-rev-parse-disambiguation.sh | 8 +--
t/t2102-update-index-symlinks.sh | 2 +-
t/t3030-merge-recursive.sh | 2 +-
t/t3100-ls-tree-restrict.sh | 2 +-
t/t3101-ls-tree-dirname.sh | 2 +-
t/t3210-pack-refs.sh | 2 +-
t/t3403-rebase-skip.sh | 2 +-
t/t3511-cherry-pick-x.sh | 14 ++---
t/t3600-rm.sh | 4 +-
t/t3700-add.sh | 16 +++---
t/t3905-stash-include-untracked.sh | 4 +-
t/t3910-mac-os-precompose.sh | 16 +++---
t/t4006-diff-mode.sh | 2 +-
t/t4010-diff-pathspec.sh | 4 +-
t/t4012-diff-binary.sh | 16 +++---
t/t4013-diff-various.sh | 6 +-
t/t4014-format-patch.sh | 10 ++--
t/t4036-format-patch-signer-mime.sh | 2 +-
t/t4038-diff-combined.sh | 2 +-
t/t4057-diff-combined-paths.sh | 2 +-
t/t4116-apply-reverse.sh | 12 ++--
t/t4119-apply-config.sh | 2 +-
t/t4204-patch-id.sh | 4 +-
t/t5000-tar-tree.sh | 6 +-
t/t5003-archive-zip.sh | 2 +-
t/t5100-mailinfo.sh | 12 ++--
t/t5300-pack-object.sh | 18 +++---
t/t5301-sliding-window.sh | 14 ++---
t/t5302-pack-index.sh | 34 ++++++------
t/t5303-pack-corruption-resilience.sh | 8 +--
t/t5304-prune.sh | 2 +-
t/t5305-include-tag.sh | 8 +--
t/t5500-fetch-pack.sh | 16 +++---
t/t5505-remote.sh | 2 +-
t/t5506-remote-groups.sh | 2 +-
t/t5510-fetch.sh | 10 ++--
t/t5515-fetch-merge-logic.sh | 4 +-
t/t5516-fetch-push.sh | 4 +-
t/t5517-push-mirror.sh | 2 +-
t/t5520-pull.sh | 10 ++--
t/t5522-pull-symlink.sh | 2 +-
t/t5530-upload-pack-error.sh | 2 +-
t/t5537-fetch-shallow.sh | 4 +-
t/t5538-push-shallow.sh | 4 +-
t/t5550-http-fetch-dumb.sh | 8 +--
t/t5551-http-fetch-smart.sh | 2 +-
t/t5570-git-daemon.sh | 8 +--
t/t5601-clone.sh | 2 +-
t/t5700-clone-reference.sh | 2 +-
t/t5710-info-alternate.sh | 2 +-
t/t5900-repo-selection.sh | 2 +-
t/t6001-rev-list-graft.sh | 12 ++--
t/t6002-rev-list-bisect.sh | 6 +-
t/t6015-rev-list-show-all-parents.sh | 6 +-
t/t6032-merge-large-rename.sh | 2 +-
t/t6034-merge-rename-nocruft.sh | 2 +-
t/t6132-pathspec-exclude.sh | 2 +-
t/t7001-mv.sh | 4 +-
t/t7003-filter-branch.sh | 6 +-
t/t7004-tag.sh | 16 +++---
t/t7006-pager.sh | 2 +-
t/t7103-reset-bare.sh | 2 +-
t/t7406-submodule-update.sh | 4 +-
t/t7408-submodule-reference.sh | 2 +-
t/t7504-commit-msg-hook.sh | 2 +-
t/t7505-prepare-commit-msg-hook.sh | 32 +++++------
t/t7602-merge-octopus-many.sh | 8 +--
t/t7700-repack.sh | 4 +-
t/t8003-blame-corner-cases.sh | 4 +-
t/t9001-send-email.sh | 10 ++--
t/t9100-git-svn-basic.sh | 24 ++++----
t/t9101-git-svn-props.sh | 30 +++++-----
t/t9104-git-svn-follow-parent.sh | 48 ++++++++--------
t/t9105-git-svn-commit-diff.sh | 4 +-
t/t9107-git-svn-migrate.sh | 16 +++---
t/t9108-git-svn-glob.sh | 20 +++----
t/t9109-git-svn-multi-glob.sh | 32 +++++------
t/t9110-git-svn-use-svm-props.sh | 2 +-
t/t9114-git-svn-dcommit-merge.sh | 12 ++--
t/t9118-git-svn-funky-branch-names.sh | 2 +-
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 +-
t/test-lib-functions.sh | 8 +--
unimplemented.sh | 2 +-
142 files changed, 609 insertions(+), 609 deletions(-)
--
1.7.10.4
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
git-stash.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t1100-commit-tree-options.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
git-web--browse.sh | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t1003-read-tree-prefix.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t0026-eol-config.sh | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t0010-racy-git.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t0001-init.sh | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
@@ -262,7 +262,7 @@ test_expect_success 'init honors global core.sharedRepository' 'gitinit)&&testx0666=\-x`gitconfig-fshared-honor-global/.git/configcore.sharedRepository`+x$(gitconfig-fshared-honor-global/.git/configcore.sharedRepository)' test_expect_success'init rejects insanely long --template''
@@ -374,7 +374,7 @@ test_expect_success 'init prefers command line to GIT_DIR' ' test_expect_success'init with separate gitdir''rm-rfnewdir&&gitinit--separate-git-dirrealgitdirnewdir&&-echo"gitdir: `pwd`/realgitdir">expected&&+echo"gitdir: $(pwd)/realgitdir">expected&&test_cmpexpectednewdir/.git&&test-drealgitdir/refs'
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
git-rebase--merge.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t3210-pack-refs.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
@@ -25,7 +25,7 @@ SHA1= test_expect_success\'see if git show-ref works as expected'\'gitbrancha&&-SHA1=`cat.git/refs/heads/a`&&+SHA1=$(cat.git/refs/heads/a)&&echo"$SHA1 refs/heads/a">expect&&gitshow-refa>result&&test_cmpexpectresult'
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t3403-rebase-skip.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
@@ -67,7 +67,7 @@ test_expect_success 'rebase --skip with --merge' '' test_expect_success'merge and reference trees equal''-test-z"`git diff-tree skip-merge skip-reference`"+test-z"$(gitdiff-treeskip-mergeskip-reference)"' test_expect_success'moved back to branch correctly''
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t3600-rm.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t1512-rev-parse-disambiguation.sh | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t3910-mac-os-precompose.sh | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t3101-ls-tree-dirname.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t4012-diff-binary.sh | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5300-pack-object.sh | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
@@ -252,8 +252,8 @@ test_expect_success \ test_expect_success\'verify-pack catches a corrupted sum of the index file itself'\-'l=`wc-c<test-3.idx`&&-l=`expr$l-20`&&+'l=$(wc-c<test-3.idx)&&+l=$(expr$l-20)&&cattest-1-${packname_1}.pack>test-3.pack&&printf"%20s"""|ddof=test-3.idxcount=20bs=1conv=notruncseek=$l&&ifgitverify-packtest-3.pack
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t4038-diff-combined.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t4010-diff-pathspec.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t4057-diff-combined-paths.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
@@ -5,7 +5,7 @@ test_description='combined diff show only paths that are different to all parent ../test-lib.sh# verify that diffc.expect matches output of-# `git diff -c --name-only HEAD HEAD^ HEAD^2`+# $(git diff -c --name-only HEAD HEAD^ HEAD^2) diffc_verify(){gitdiff-c--name-onlyHEADHEAD^HEAD^2>diffc.actual&&test_cmpdiffc.expectdiffc.actual
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5500-fetch-pack.sh | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5303-pack-corruption-resilience.sh | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t4014-format-patch.sh | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t4036-format-patch-signer-mime.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
@@ -42,7 +42,7 @@ test_expect_success 'attach and signoff do not duplicate mime headers' 'GIT_COMMITTER_NAME="はまの ふにおう"\gitformat-patch-s--stdout-1--attach>output&&-test`grep-ci^MIME-Version:output`=1+test$(grep-ci^MIME-Version:output)=1'
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5700-clone-reference.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5520-pull.sh | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
@@ -94,9 +94,9 @@ test_expect_success 'test . as a remote' 'echoupdated>file&&gitcommit-a-mupdated&&gitcheckoutcopy&&-test`catfile`=file&&+test$(catfile)=file&&gitpull&&-test`catfile`=updated+test$(catfile)=updated' test_expect_success'the default remote . should not break explicit pull''
@@ -105,9 +105,9 @@ test_expect_success 'the default remote . should not break explicit pull' 'gitcommit-a-mmodified&&gitcheckoutcopy&&gitreset--hardHEAD^&&-test`catfile`=file&&+test$(catfile)=file&&gitpull.second&&-test`catfile`=modified+test$(catfile)=modified' test_expect_success'--rebase''
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t6034-merge-rename-nocruft.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
@@ -117,7 +117,7 @@ test_expect_success 'merge blue into white (A->B, mod A, A untracked)' \echo"BAD: A does not exist in working directory"return1}-test`catA`=dirty||{+test$(catA)=dirty||{echo"BAD: A content is wrong"return1}
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5538-push-shallow.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
@@ -104,7 +104,7 @@ EOF' test_expect_success'push from full to shallow''-!git--git-dir=shallow2/.gitcat-fileblob`echo1|githash-object--stdin`&&+!git--git-dir=shallow2/.gitcat-fileblob$(echo1|githash-object--stdin)&&commit1&&gitpushshallow2/.git+master:refs/remotes/top/master&&(
@@ -117,7 +117,7 @@ test_expect_success 'push from full to shallow' '3 EOFtest_cmpexpectactual&&-gitcat-fileblob`echo1|githash-object--stdin`>/dev/null+gitcat-fileblob$(echo1|githash-object--stdin)>/dev/null)'
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5517-push-mirror.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5505-remote.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5100-mailinfo.sh | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5530-upload-pack-error.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t7004-tag.sh | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
@@ -23,8 +23,8 @@ test_expect_success 'listing all tags in an empty tree should succeed' '' test_expect_success'listing all tags in an empty tree should output nothing''-test`gittag-l|wc-l`-eq0&&-test`gittag|wc-l`-eq0+test$(gittag-l|wc-l)-eq0&&+test$(gittag|wc-l)-eq0' test_expect_success'looking for a tag in an empty tree should fail'\
@@ -60,8 +60,8 @@ test_expect_success 'listing all tags if one exists should succeed' '' test_expect_success'listing all tags if one exists should output that tag''-test`gittag-l`=mytag&&-test`gittag`=mytag+test$(gittag-l)=mytag&&+test$(gittag)=mytag'# pattern matching:
@@ -71,7 +71,7 @@ test_expect_success 'listing a tag using a matching pattern should succeed' \ test_expect_success\'listing a tag using a matching pattern should output that tag'\-'test `git tag -l mytag` = mytag'+'test $(git tag -l mytag) = mytag'# todo: git tag -l now returns always zero, when fixed, change this test test_expect_success\
@@ -80,7 +80,7 @@ test_expect_success \ test_expect_success\'listing tags using a non-matching pattern should output nothing'\-'test `git tag -l xxx | wc -l` -eq 0'+'test $(git tag -l xxx | wc -l) -eq 0'# special cases for creating tags:
@@ -90,13 +90,13 @@ test_expect_success \ test_expect_success\'trying to create a tag with a non-valid name should fail''-test`gittag-l|wc-l`-eq1&&+test$(gittag-l|wc-l)-eq1&&test_must_failgittag""&&test_must_failgittag.othertag&&test_must_failgittag"other tag"&&test_must_failgittag"othertag^"&&test_must_failgittag"other~tag"&&-test`gittag-l|wc-l`-eq1+test$(gittag-l|wc-l)-eq1' test_expect_success'creating a tag using HEAD directly should succeed''
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t6132-pathspec-exclude.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5710-info-alternate.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t4116-apply-reverse.sh | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
@@ -30,10 +30,10 @@ test_expect_success setup ' test_expect_success'apply in forward''-T0=`gitrev-parse"second^{tree}"`&&+T0=$(gitrev-parse"second^{tree}")&&gitreset--hardinitial&&gitapply--index--binarypatch&&-T1=`gitwrite-tree`&&+T1=$(gitwrite-tree)&&test"$T0"="$T1"'
@@ -62,22 +62,22 @@ test_expect_success 'setup separate repository lacking postimage' ' test_expect_success'apply in forward without postimage''-T0=`gitrev-parse"second^{tree}"`&&+T0=$(gitrev-parse"second^{tree}")&&(cdinitial&&gitapply--index--binary../patch&&-T1=`gitwrite-tree`&&+T1=$(gitwrite-tree)&&test"$T0"="$T1")' test_expect_success'apply in reverse without postimage''-T0=`gitrev-parse"initial^{tree}"`&&+T0=$(gitrev-parse"initial^{tree}")&&(cdsecond&&gitapply--index--binary--reverse../patch&&-T1=`gitwrite-tree`&&+T1=$(gitwrite-tree)&&test"$T0"="$T1")'
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t6032-merge-large-rename.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5537-fetch-shallow.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
@@ -98,7 +98,7 @@ EOF test_expect_success'fetch something upstream has but hidden by clients shallow boundaries''# the blob "1" is available in .git but hidden by the# shallow2/.git/shallow and it should be resent-!git--git-dir=shallow2/.gitcat-fileblob`echo1|githash-object--stdin`>/dev/null&&+!git--git-dir=shallow2/.gitcat-fileblob$(echo1|githash-object--stdin)>/dev/null&&echo1>1.t&&gitadd1.t&&gitcommit-madd-1-back&&
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5570-git-daemon.sh | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t7406-submodule-update.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
@@ -14,8 +14,8 @@ submodule and "git submodule update --rebase/--merge" does not detach the HEAD. compare_head(){-sha_master=`gitrev-list--max-count=1master`-sha_head=`gitrev-list--max-count=1HEAD`+sha_master=$(gitrev-list--max-count=1master)+sha_head=$(gitrev-list--max-count=1HEAD)test"$sha_master"="$sha_head"}
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t7103-reset-bare.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
@@ -63,7 +63,7 @@ test_expect_success '"mixed" reset is not allowed in bare' ' test_expect_success'"soft" reset is allowed in bare''gitreset--softHEAD^&&-test"`git show --pretty=format:%s | head -n 1`"="one"+test"$(gitshow--pretty=format:%s|head-n1)"="one"' test_done
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t7003-filter-branch.sh | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t6002-rev-list-bisect.sh | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
@@ -27,9 +27,9 @@ test_bisection_diff()# Test if bisection size is close to half of list size within# tolerance.#-_bisect_err=`expr$_list_size-$_bisection_size\*2`-test"$_bisect_err"-lt0&&_bisect_err=`expr0-$_bisect_err`-_bisect_err=`expr$_bisect_err/2`;# floor+_bisect_err=$(expr$_list_size-$_bisection_size\*2)+test"$_bisect_err"-lt0&&_bisect_err=$(expr0-$_bisect_err)+_bisect_err=$(expr$_bisect_err/2);# floortest_expect_success\"bisection diff $_bisect_option$_head$* <= $_max_diff"\
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t7006-pager.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t6015-rev-list-show-all-parents.sh | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5522-pull-symlink.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
@@ -54,7 +54,7 @@ test_expect_success SYMLINKS 'pulling from real subdir' '# git rev-parse --show-cdup printed a path relative to# clone-repo/subdir/, not subdir-link/. Git rev-parse --show-cdup# used the correct .git, but when the git pull shell script did-# "cd `git rev-parse --show-cdup`", it ended up in the wrong+# "cd $(git rev-parse --show-cdup)", it ended up in the wrong# directory. A POSIX shell's "cd" works a little differently# than chdir() in C; "cd -P" is much closer to chdir().#
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5304-prune.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5301-sliding-window.sh | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5515-fetch-merge-logic.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t7001-mv.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5601-clone.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
git-rebase.sh | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
@@ -521,10 +521,10 @@ case "$#" in;;0)# Do not need to switch branches, we are already on it.-ifbranch_name=`gitsymbolic-ref-qHEAD`+ifbranch_name=$(gitsymbolic-ref-qHEAD)thenhead_name=$branch_name-branch_name=`expr"z$branch_name":'zrefs/heads/\(.*\)'`+branch_name=$(expr"z$branch_name":'zrefs/heads/\(.*\)')elsehead_name="detached HEAD"branch_name=HEAD;# detached
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5003-archive-zip.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5305-include-tag.sh | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5900-repo-selection.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5550-http-fetch-dumb.sh | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5516-fetch-push.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t4013-diff-various.sh | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5510-fetch.sh | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5000-tar-tree.sh | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5302-pack-index.sh | 34 +++++++++++++++++-----------------
1 file changed, 17 insertions(+), 17 deletions(-)
@@ -152,10 +152,10 @@ test_expect_success \'[index v1] 2) create a stealth corruption in a delta base reference'\'# This test assumes file_101 is a delta smaller than 16 bytes.# It should be against file_100 but we substitute its base for file_099-sha1_101=`githash-objectfile_101`&&-sha1_099=`githash-objectfile_099`&&-offs_101=`index_obj_offset1.idx$sha1_101`&&-nr_099=`index_obj_nr1.idx$sha1_099`&&+sha1_101=$(githash-objectfile_101)&&+sha1_099=$(githash-objectfile_099)&&+offs_101=$(index_obj_offset1.idx$sha1_101)&&+nr_099=$(index_obj_nr1.idx$sha1_099)&&chmod+w".git/objects/pack/pack-${pack1}.pack"&&ddof=".git/objects/pack/pack-${pack1}.pack"seek=$(($offs_101+1))\if=".git/objects/pack/pack-${pack1}.idx"\
@@ -193,10 +193,10 @@ test_expect_success \'[index v2] 2) create a stealth corruption in a delta base reference'\'# This test assumes file_101 is a delta smaller than 16 bytes.# It should be against file_100 but we substitute its base for file_099-sha1_101=`githash-objectfile_101`&&-sha1_099=`githash-objectfile_099`&&-offs_101=`index_obj_offset1.idx$sha1_101`&&-nr_099=`index_obj_nr1.idx$sha1_099`&&+sha1_101=$(githash-objectfile_101)&&+sha1_099=$(githash-objectfile_099)&&+offs_101=$(index_obj_offset1.idx$sha1_101)&&+nr_099=$(index_obj_nr1.idx$sha1_099)&&chmod+w".git/objects/pack/pack-${pack1}.pack"&&ddof=".git/objects/pack/pack-${pack1}.pack"seek=$(($offs_101+1))\if=".git/objects/pack/pack-${pack1}.idx"\
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t1050-large.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5551-http-fetch-smart.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t4119-apply-config.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t6001-rev-list-graft.sh | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
@@ -10,15 +10,15 @@ test_expect_success setup 'echo>subdir/fileBfileB&&gitaddfileAsubdir/fileB&&gitcommit-a-m"Initial in one history."&&-A0=`gitrev-parse--verifyHEAD`&&+A0=$(gitrev-parse--verifyHEAD)&&echo>fileAfileAmodified&&gitcommit-a-m"Second in one history."&&-A1=`gitrev-parse--verifyHEAD`&&+A1=$(gitrev-parse--verifyHEAD)&&echo>subdir/fileBfileBmodified&&gitcommit-a-m"Third in one history."&&-A2=`gitrev-parse--verifyHEAD`&&+A2=$(gitrev-parse--verifyHEAD)&&rm-f.git/refs/heads/master.git/index&&
@@ -26,15 +26,15 @@ test_expect_success setup 'echo>subdir/fileBfileBagain&&gitaddfileAsubdir/fileB&&gitcommit-a-m"Initial in alternate history."&&-B0=`gitrev-parse--verifyHEAD`&&+B0=$(gitrev-parse--verifyHEAD)&&echo>fileAfileAmodifiedinalternatehistory&&gitcommit-a-m"Second in alternate history."&&-B1=`gitrev-parse--verifyHEAD`&&+B1=$(gitrev-parse--verifyHEAD)&&echo>subdir/fileBfileBmodifiedinalternatehistory&&gitcommit-a-m"Third in alternate history."&&-B2=`gitrev-parse--verifyHEAD`&&+B2=$(gitrev-parse--verifyHEAD)&&:done'
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t5506-remote-groups.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t4006-diff-mode.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t4204-patch-id.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t1401-symbolic-ref.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t0300-credentials.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t1004-read-tree-m-u-wf.sh | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
@@ -54,7 +54,7 @@ test_expect_success 'two-way with incorrect --exclude-per-directory (1)' ' test_expect_success'two-way with incorrect --exclude-per-directory (2)''-iferr=`read_tree_u_must_succeed-m-u--exclude-per-directory=foo--exclude-per-directory=.gitignoremasterside2>&1`+iferr=$(read_tree_u_must_succeed-m-u--exclude-per-directory=foo--exclude-per-directory=.gitignoremasterside2>&1)thenechoshouldhavecomplainedfalse
@@ -95,7 +95,7 @@ test_expect_success 'three-way not clobbering a working tree file' 'gitcheckoutmaster&&echo>file3filethreecreatedinmaster,untracked&&echo>subdir/file3filethreecreatedinmaster,untracked&&-iferr=`read_tree_u_must_succeed-m-ubranch-pointmasterside2>&1`+iferr=$(read_tree_u_must_succeed-m-ubranch-pointmasterside2>&1)thenechoshouldhavecomplainedfalse
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t3030-merge-recursive.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t1002-read-tree-m-u-2way.sh | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t1511-rev-parse-caret.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical method for command substitution,
and is supported by POSIX. However, all but the simplest uses become
complicated quickly. In particular, embedded command substitutions
and/or the use of double quotes require careful escaping with the backslash
character. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.
The patch was generated by the simple script
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
Signed-off-by: Elia Pinto <redacted>
---
t/t3700-add.sh | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
@@ -33,7 +33,7 @@ test_expect_success \ test_expect_success'git add: filemode=0 should not get confused by symlink''rm-fxfoo1&&test_ln_s_addfooxfoo1&&-case"`git ls-files --stage xfoo1`"in+case"$(gitls-files--stagexfoo1)"in120000" "*xfoo1)echopass;;*)echofail;gitls-files--stagexfoo1;(exit1);;esac
@@ -53,7 +53,7 @@ test_expect_success \ test_expect_success'git add: filemode=0 should not get confused by symlink''rm-fxfoo2&&test_ln_s_addfooxfoo2&&-case"`git ls-files --stage xfoo2`"in+case"$(gitls-files--stagexfoo2)"in120000" "*xfoo2)echopass;;*)echofail;gitls-files--stagexfoo2;(exit1);;esac
@@ -63,7 +63,7 @@ test_expect_success \'git update-index --add: Test that executable bit is not used...'\'gitconfigcore.filemode0&&test_ln_s_addxfoo2xfoo3&&# runs git update-index --add-case"`git ls-files --stage xfoo3`"in+case"$(gitls-files--stagexfoo3)"in120000" "*xfoo3)echopass;;*)echofail;gitls-files--stagexfoo3;(exit1);;esac'
@@ -166,14 +166,14 @@ test_expect_success 'git add with filemode=0, symlinks=0 prefers stage 2 over st test_expect_success'git add --refresh''>foo&&gitaddfoo&&gitcommit-a-m"commit all"&&-test-z"`git diff-index HEAD -- foo`"&&+test-z"$(gitdiff-indexHEAD--foo)"&&gitread-treeHEAD&&-case"`git diff-index HEAD -- foo`"in+case"$(gitdiff-indexHEAD--foo)"in:100644" "*"M foo")echopass;;*)echofail;(exit1);;esac&&gitadd--refresh--foo&&-test-z"`git diff-index HEAD -- foo`"+test-z"$(gitdiff-indexHEAD--foo)"' test_expect_success'git add --refresh with pathspec''