From: Clemens Buchacher <drizzd@aon.at>
To: Ben Walton <bwalton@artsci.utoronto.ca>
Cc: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>,
git <git@vger.kernel.org>, gitster <gitster@pobox.com>,
"Jeff King" <peff@peff.net>
Subject: Re: [PATCH] git-daemon wrapper to wait until daemon is ready
Date: Sat, 14 Apr 2012 21:00:56 +0200 [thread overview]
Message-ID: <20120414190056.GC3915@ecki> (raw)
In-Reply-To: <1334428952-sup-5241@pinkfloyd.chass.utoronto.ca>
On Sat, Apr 14, 2012 at 02:43:41PM -0400, Ben Walton wrote:
>
> > The shell script which is currently used to parse git daemon output does
> > not seem to work unreliably. In order to work around such issues,
>
> Presumably you mean "work reliably" here?
Yes, that's what I meant the commit message to say. Thanks for noticing.
But I would like to wait for more info from the OP before we conclude
that this is indeed the case.
next prev parent reply other threads:[~2012-04-14 19:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-14 18:29 [PATCH] git-daemon wrapper to wait until daemon is ready Clemens Buchacher
2012-04-14 18:32 ` [PATCH] t5570: use explicit push refspec Clemens Buchacher
2012-04-14 23:40 ` Junio C Hamano
2012-04-15 0:11 ` Clemens Buchacher
2012-04-15 19:20 ` Junio C Hamano
2012-04-15 19:52 ` Clemens Buchacher
2012-04-15 20:18 ` Junio C Hamano
2012-04-14 18:43 ` [PATCH] git-daemon wrapper to wait until daemon is ready Ben Walton
2012-04-14 19:00 ` Clemens Buchacher [this message]
2012-04-14 19:16 ` [PATCH v2] " Clemens Buchacher
2012-04-14 19:36 ` [PATCH] " Johannes Sixt
2012-04-14 22:06 ` Clemens Buchacher
2012-04-15 11:53 ` [PATCH v3] " Clemens Buchacher
2012-04-16 15:46 ` Zbigniew Jędrzejewski-Szmek
2012-04-19 15:00 ` Junio C Hamano
2012-04-15 17:11 ` [PATCH] " Johannes Sixt
2012-04-15 19:32 ` Clemens Buchacher
2012-04-15 19:57 ` Johannes Sixt
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=20120414190056.GC3915@ecki \
--to=drizzd@aon.at \
--cc=bwalton@artsci.utoronto.ca \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).