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@xxxxxxxxxx about it and mention the name of the problematic repo. I'll look into the weird routing thing that Carlos mentioned, too. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html