From: John Szakmeister <john@szakmeister.net>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>
Subject: Re: [BUG] clone: regression in error messages in master
Date: Fri, 21 Jun 2013 06:07:07 -0400 [thread overview]
Message-ID: <CAEBDL5UNNHnogHb2ztq2G8OxyCNMoLia7xYFNSy+kfHD3pS1pQ@mail.gmail.com> (raw)
In-Reply-To: <CALkWK0n7S8s-ABQ1qV5JSsyhYo6=rmK1UT+uYW9hjjeWjambug@mail.gmail.com>
On Thu, Jun 20, 2013 at 9:16 AM, Ramkumar Ramachandra
<artagnon@gmail.com> 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).
-John
next prev parent reply other threads:[~2013-06-21 10:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 13:16 [BUG] clone: regression in error messages in master Ramkumar Ramachandra
2013-06-20 13:34 ` Jeff King
2013-06-21 6:44 ` Ramkumar Ramachandra
2013-06-21 6:46 ` Ramkumar Ramachandra
2013-06-21 7:05 ` Jeff King
2013-06-21 16:03 ` Junio C Hamano
2013-06-21 10:07 ` John Szakmeister [this message]
2013-06-21 17:11 ` Junio C Hamano
2013-06-22 9:55 ` John Szakmeister
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEBDL5UNNHnogHb2ztq2G8OxyCNMoLia7xYFNSy+kfHD3pS1pQ@mail.gmail.com \
--to=john@szakmeister.net \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).