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

Re: Multiple Keys in ssh-agent, fail to clone

From
BFBenjamin Fritsch <beanie@benle.de>
Date
Jul 15, 2016, 12:04 UTC
Message-ID
<7128CED1-381C-4489-A26D-3645D5A7BB69@benle.de>
In-Reply-To
<xmqqziplz63l.fsf@gitster.mtv.corp.google.com>
Show 9 quoted lines
> On Jul 13, 2016, at 3:32 PM, Junio C Hamano <gitster@pobox.com> wrote:
> 
> Benjamin Fritsch <beanie@benle.de> writes:
> 
>> I read the Changelog for 2.9 and couldn’t find any reference to changed key handling. Is there anything that I can add to the `git clone` command to get the old behavior?
> 
> I do not think this has much to do with the version of Git, unless
> you are getting an updated SSH client together with your new version
> of Git from whoever distributes it.

Thank you for the great feedback. I could confirm that this is a problem on Bitbucket’s end. Sorry for the confusion. I managed to successfully clone with Git 2.9 and Git 2.8

Best, ben

Previous: Junio C HamanoNext: Johannes Schindelin
Message 3 of 4 in “Multiple Keys in ssh-agent, fail to clone”
  1. Benjamin FritschJul 13, 2016
  2. Junio C HamanoJul 13, 2016
  3. Benjamin FritschJul 15, 2016
  4. Johannes SchindelinJul 14, 2016

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.