From: "Torsten Bögershausen" <tboegi@web.de>
To: "Torsten Bögershausen" <tboegi@web.de>,
"Jonathan Nieder" <jrnieder@gmail.com>
Cc: "Kyle J. McKay" <mackyle@gmail.com>,
Git mailing list <git@vger.kernel.org>
Subject: Re: git_inetd_server: run git-http-backend using inetd
Date: Sun, 20 Jul 2014 17:25:46 +0200 [thread overview]
Message-ID: <53CBDF7A.5040509@web.de> (raw)
In-Reply-To: <53CB5D64.9060801@web.de>
On 07/20/2014 08:10 AM, Torsten Bögershausen wrote:
> On 07/19/2014 07:06 PM, Jonathan Nieder wrote:
>> Torsten Bögershausen wrote:
>>
>>> Jonathan, (I'm good in searching, but bad in finding)
>>> could you point out where the source code for the git package for
>>> debian is ?
>>>
>>> I recently learned about mDNS, and will probably do some tests
>>> and experiments later, and would like to test the lookup feature
>>> of "0010".
>> Thanks. It's at git://git.debian.org/~jrnieder-guest/git branch
>> release+patches and mirrored at http://repo.or.cz/r/git/debian
I probably need to correct myself:
Donwloaded your branch, compiled and tested.
On my test system the lookup timed out after 1.9 sec for DNS,
and 5 seconds for MDNS (the lookup failed in both cases)
I'm not sure any more how to improve things here, and
the question remains why Kyle has 15 seconds timeout ?
Would it be possible to run wireshark, and give us an example
of the URL's you have been using ?
prev parent reply other threads:[~2014-07-20 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 21:28 git_inetd_server: run git-http-backend using inetd Kyle J. McKay
2014-07-17 22:10 ` Jonathan Nieder
2014-07-17 23:38 ` Kyle J. McKay
2014-07-18 2:22 ` Jonathan Nieder
2014-07-18 6:48 ` Kyle J. McKay
2014-07-18 17:16 ` Jonathan Nieder
2014-07-19 0:08 ` Kyle J. McKay
2014-07-19 0:19 ` Jonathan Nieder
2014-07-19 1:54 ` Kyle J. McKay
2014-07-19 6:21 ` Torsten Bögershausen
2014-07-19 17:06 ` Jonathan Nieder
2014-07-20 6:10 ` Torsten Bögershausen
2014-07-20 15:25 ` Torsten Bögershausen [this message]
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=53CBDF7A.5040509@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=mackyle@gmail.com \
/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).