From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Egor Ryabkov" <egor.ryabkov@gmail.com>,
git@vger.kernel.org, "Carlos Martín Nieto" <cmn@elego.de>
Subject: Re: Git fetch/pull stopped working
Date: Tue, 8 May 2012 16:08:42 -0400 [thread overview]
Message-ID: <20120508200842.GA14779@sigill.intra.peff.net> (raw)
In-Reply-To: <7v8vh2v501.fsf@alter.siamese.dyndns.org>
On Tue, May 08, 2012 at 12:37:18PM -0700, Junio C Hamano wrote:
> But as I said, "ERROR: Repository not found." does not seem to match any
> message of the released version of Git, so I cannot even tell where it is
> failing.
>
> It could be that the message is coming from a customized version of ssh
> login handler github uses to shard and map the user accounts to
> directories[...]
That is exactly where it comes from.
> if they were running the vanilla Git), and if that is the case,
> perhaps the argument thrown at git-upload-pack from your local box and
> the problematic box somehow look different to Github, but that is in
> the "(REDACTED)" part, so I cannot tell from what was pasted in the
> pastebin.
Agreed. It's hard to tell if there's a real problem or not. If the
redacted bits are the same, then it is probably a github issue. In that
case, Egor, you should email support@github.com about it and mention the
name of the problematic repo.
I'll look into the weird routing thing that Carlos mentioned, too.
-Peff
next prev parent reply other threads:[~2012-05-08 20:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 22:45 Git fetch/pull stopped working Egor Ryabkov
2012-05-07 23:44 ` Junio C Hamano
2012-05-08 0:10 ` Carlos Martín Nieto
2012-05-08 20:18 ` Jeff King
2012-05-08 13:59 ` Egor Ryabkov
2012-05-08 19:37 ` Junio C Hamano
2012-05-08 20:08 ` Jeff King [this message]
2012-05-08 20:29 ` Carlos Martín Nieto
2012-05-08 21:28 ` Egor Ryabkov
2012-05-11 18:47 ` Egor Ryabkov
2012-05-11 19:55 ` jaseem abid
2012-05-11 20:28 ` 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=20120508200842.GA14779@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=cmn@elego.de \
--cc=egor.ryabkov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).