From: Andreas Schwab <schwab@redhat.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: git torvalds/linux-2.6.git gives obscure results
Date: Fri, 03 Jun 2011 14:05:55 +0200 [thread overview]
Message-ID: <m38vtjglwc.fsf@redhat.com> (raw)
In-Reply-To: <201106031317.35112.toralf.foerster@gmx.de> ("Toralf Förster"'s message of "Fri, 3 Jun 2011 13:17:34 +0200")
Toralf Förster <toralf.foerster@gmx.de> writes:
> at the command line. And within a sniffed network stream w/ wireshark I can
> see something like :
>
> 0059git-upload-pack
> /pub/scm/linux/kernel/git/torvalds/linux-2.6.git.host=git.kernel.org.git:
> 'daemon' is not a git command. See 'git --help'.
Odd thing is that it only fails like that half of the time.
Andreas.
--
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 5EC7 45C6 250E 6F00 984E
"And now for something completely different."
prev parent reply other threads:[~2011-06-03 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 11:17 git torvalds/linux-2.6.git gives obscure results Toralf Förster
2011-06-03 11:29 ` richard -rw- weinberger
2011-06-03 12:36 ` Bjørn Mork
2011-06-03 15:27 ` Andrew Watts
2011-06-03 12:05 ` Andreas Schwab [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=m38vtjglwc.fsf@redhat.com \
--to=schwab@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
/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