From: Clemens Buchacher <drizzd@aon.at>
To: Johannes Sixt <j6t@kdbg.org>
Cc: "Jeff King" <peff@peff.net>,
"Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>,
git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] t5570: forward git-daemon messages in a different way
Date: Thu, 26 Apr 2012 21:55:04 +0200 [thread overview]
Message-ID: <20120426195503.GA29526@ecki> (raw)
In-Reply-To: <4F999105.200@kdbg.org>
On Thu, Apr 26, 2012 at 08:16:37PM +0200, Johannes Sixt wrote:
>
> @@ -30,10 +30,10 @@ start_git_daemon() {
> "$@" "$GIT_DAEMON_DOCUMENT_ROOT_PATH" \
> >&3 2>git_daemon_output &
> GIT_DAEMON_PID=$!
> + exec 7<git_daemon_output &&
> {
> - read line
> + read line <&7
> echo >&4 "$line"
> - cat >&4 &
>
> # Check expected output
> if test x"$(expr "$line" : "\[[0-9]*\] \(.*\)")" != x"Ready to rumble"
> @@ -43,7 +43,9 @@ start_git_daemon() {
> trap 'die' EXIT
> error "git daemon failed to start"
> fi
> - } <git_daemon_output
> + cat <&7 >&4 &
> + exec 7<&-
> + }
I won't pretend to understand why this works. I have to study this some
more. But if this is 'correct', then it is obviously preferable to the
comparatively complicated wrapper.
We should move the cat <&7 >&4 & and exec 7<&- part in front of the
output check, otherwise output would be truncated in an error condition.
This can be tested by passing an invalid argument to git daemon above,
for example.
Clemens
next prev parent reply other threads:[~2012-04-26 20:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-14 8:44 [PATCH] t5570: forward git-daemon messages in a different way Zbigniew Jędrzejewski-Szmek
2012-04-14 12:13 ` Clemens Buchacher
2012-04-14 12:21 ` Clemens Buchacher
2012-04-16 15:43 ` Zbigniew Jędrzejewski-Szmek
2012-04-16 17:09 ` Junio C Hamano
2012-04-16 21:22 ` Clemens Buchacher
2012-04-16 22:06 ` Zbigniew Jędrzejewski-Szmek
2012-04-17 15:43 ` Junio C Hamano
2012-04-16 17:42 ` Jeff King
2012-04-16 22:44 ` Clemens Buchacher
2012-04-19 6:03 ` Jeff King
2012-04-19 6:58 ` Johannes Sixt
2012-04-26 13:01 ` Jeff King
2012-04-26 18:16 ` Johannes Sixt
2012-04-26 19:55 ` Clemens Buchacher [this message]
2012-04-26 21:00 ` [PATCH] t5570: fix forwarding of git-daemon messages via cat Johannes Sixt
2012-04-26 21:10 ` Zbigniew Jędrzejewski-Szmek
2012-04-27 7:59 ` Jeff King
2012-04-27 15:02 ` Junio C Hamano
2012-04-27 7:55 ` [PATCH] t5570: forward git-daemon messages in a different way Jeff King
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=20120426195503.GA29526@ecki \
--to=drizzd@aon.at \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=peff@peff.net \
--cc=zbyszek@in.waw.pl \
/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).