John Szakmeister <john@xxxxxxxxxxxxxxx> writes: > On Thu, Jun 20, 2013 at 9:16 AM, Ramkumar Ramachandra > <artagnon@xxxxxxxxx> wrote: >> Hi, >> >> So this should explain the problem: >> >> # using v1.8.3.1 >> $ git clone https://google.com >> Cloning into 'google.com'... >> fatal: repository 'https://google.com/' not found >> >> # using master >> $ git clone https://google.com >> Cloning into 'google.com'... >> fatal: repository 'https://google.com/' not found >> fatal: Reading from helper 'git-remote-https' failed > > I can see where this is confusing, but can also see how it's useful > information to have. On clone, it's probably not that useful since > you're looking right at the url, but I could see that information > being more useful on a pull or push with the default arguments (when > the source and destination aren't quite as obvious). The "extra" error messages is not the first one, but the last one, and the suggested revert is a proposal to remove the latter, not the "repository $URL not found". -- 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