git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Johannes Sixt <j6t@kdbg.org>
Subject: [PATCH 1/3] git-remote-testgit: avoid process substitution
Date: Mon, 29 Apr 2013 10:41:53 -0700	[thread overview]
Message-ID: <1367257315-12009-2-git-send-email-gitster@pobox.com> (raw)
In-Reply-To: <1367257315-12009-1-git-send-email-gitster@pobox.com>

From: Johannes Sixt <j6t@kdbg.org>

The implementation of bash on Windows does not offer process substitution.

Signed-off-by: Johannes Sixt <j6t@kdbg.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 git-remote-testgit | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/git-remote-testgit b/git-remote-testgit
index 5fd09f9..643e4ae 100755
--- a/git-remote-testgit
+++ b/git-remote-testgit
@@ -86,17 +86,18 @@ do
 			exit 1
 		fi
 
-		before=$(git for-each-ref --format='%(refname) %(objectname)')
+		before=$(git for-each-ref --format=' %(refname) %(objectname) ')
 
 		git fast-import "${testgitmarks_args[@]}" --quiet
 
-		after=$(git for-each-ref --format='%(refname) %(objectname)')
-
 		# figure out which refs were updated
-		join -e 0 -o '0 1.2 2.2' -a 2 <(echo "$before") <(echo "$after") |
-		while read ref a b
+		git for-each-ref --format='%(refname) %(objectname)' |
+		while read ref a
 		do
-			test $a == $b && continue
+			case "$before" in
+			*" $ref $a "*)
+				continue ;;	# unchanged
+			esac
 			echo "ok $ref"
 		done
 
-- 
1.8.3-rc0-121-gda9b90f

  reply	other threads:[~2013-04-29 17:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22 20:07 What's cooking in git.git (Apr 2013, #07; Mon, 22) Junio C Hamano
2013-04-23 19:31 ` What's cooking in git.git (Apr 2013, #08; Tue, 23) Junio C Hamano
2013-04-24  7:57   ` Johannes Sixt
2013-04-24  8:04     ` Felipe Contreras
2013-04-24  8:30       ` Johannes Sixt
2013-04-25  5:56         ` [PATCH] git-remote-testgit: avoid process substitution Johannes Sixt
2013-04-25 14:57           ` Junio C Hamano
2013-04-25 17:50             ` Felipe Contreras
2013-04-25 18:25               ` Junio C Hamano
2013-04-25 19:24                 ` Felipe Contreras
2013-04-25 20:06                   ` Junio C Hamano
2013-04-25 20:31                     ` Felipe Contreras
2013-04-26 21:56           ` Felipe Contreras
2013-04-26 22:25             ` Junio C Hamano
2013-04-26 22:45               ` Felipe Contreras
2013-04-26 23:26                 ` Re* " Junio C Hamano
2013-04-27 19:13                   ` Johannes Sixt
2013-04-29 17:36                     ` Junio C Hamano
2013-04-29 17:41                       ` [PATCH 0/3] De-bashing remote-testgit Junio C Hamano
2013-04-29 17:41                         ` Junio C Hamano [this message]
2013-04-29 17:41                         ` [PATCH 2/3] git-remote-testgit: further remove some bashisms Junio C Hamano
2013-04-29 17:41                         ` [PATCH 3/3] git-remote-testgit: build it to run under $SHELL_PATH 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=1367257315-12009-2-git-send-email-gitster@pobox.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.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).