git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [BUG] clone: regression in error messages in master

From
John Szakmeister <john@szakmeister.net>
Date
Jun 22, 2013, 09:55 UTC
Message-ID
<CAEBDL5WYCdMEOsoXtxgfNDmJrkj2DR8DgTwKY72iUJjQyJ-bRw@mail.gmail.com>
In-Reply-To
<7vli63mlro.fsf@alter.siamese.dyndns.org>
On Fri, Jun 21, 2013 at 1:11 PM, Junio C Hamano <gitster@pobox.com> wrote:
> John Szakmeister <john@szakmeister.net> writes:
[snip]
Show 9 quoted lines
>> 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".

Sorry for the confusion. I realize they were talking about removing the remote helper line. What I meant was that with the url there, it's a bit easier to determine which part of git failed (http, hg, or bzr remote helper, for instance). What I was trying to say was perhaps there are paths through here where it's really helpful to know that things failed in the remote helper, so we may not want to wholesale remove it. Some of remote helpers, such as ones that talk to foreign VCSes, do quite a bit more than just transfer data, so it might be helpful to know that it's not core git that's failing but the remote helper. Seeing the URL is a reminder that you're interacting with a remote helper, and it may not be helpful there. But other commands don't necessarily show that to you, and it may be more helpful to have that reminder that it was a remote helper that failed.

I hope that makes more sense.
-John
Previous: Junio C Hamano
Message 9 of 9 in “[BUG] clone: regression in error messages in master”
  1. Ramkumar RamachandraJun 20, 2013
  2. Jeff KingJun 20, 2013
  3. Ramkumar RamachandraJun 21, 2013
  4. Ramkumar RamachandraJun 21, 2013
  5. Jeff KingJun 21, 2013
  6. Junio C HamanoJun 21, 2013
  7. John SzakmeisterJun 21, 2013
  8. Junio C HamanoJun 21, 2013
  9. John SzakmeisterJun 22, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.