From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: fetch failure from git2.kernel.org?
Date: Sun, 22 Apr 2007 05:56:42 -0700 [thread overview]
Message-ID: <86ps5wr2id.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <20070422125307.GA2431@steel.home> (Alex Riesen's message of "Sun, 22 Apr 2007 14:53:07 +0200")
>>>>> "Alex" == Alex Riesen <raa.lkml@gmail.com> writes:
Alex> Confirm this. BTW, git1 and git2 point to the same 140.211.167.38
Alex> (poseidon.kernel.org). It used to be different addresses
Ahh, that's why it didn't help to try changing it. :)
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2007-04-22 12:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-22 10:03 fetch failure from git2.kernel.org? Randal L. Schwartz
2007-04-22 12:53 ` Alex Riesen
2007-04-22 12:56 ` Randal L. Schwartz [this message]
2007-04-22 14:20 ` Petr Baudis
2007-04-22 17:53 ` Linus Torvalds
2007-04-22 18:26 ` 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=86ps5wr2id.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=git@vger.kernel.org \
--cc=raa.lkml@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.