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

Re: Ambiguous sha-1 during a rebase

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Apr 14, 2016, 15:55 UTC
Message-ID
<alpine.DEB.2.20.1604141754371.2967@virtualbox>
In-Reply-To
<xmqqr3e9i10b.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Wed, 13 Apr 2016, Junio C Hamano wrote:
Show 6 quoted lines
> Mike Hommey <mh@glandium.org> writes:
> 
> > Should git-rebase use full sha-1s under the hood to avoid these type of
> > races?
> 
> It already should be doing so since Aug 2013, IIRC.

Indeed. It is one of the things that makes interactive rebases so unbearably slow on Windows (because that transformation results in tons of spawned processes, which is slow on Windows, and even worse: tons of POSIX-emulated processes, which is even slower).

Ciao, Dscho

Previous: Remi Galan Alfonso
Message 8 of 8 in “Ambiguous sha-1 during a rebase”
  1. Mike HommeyApr 13, 2016
  2. Junio C HamanoApr 13, 2016
  3. Mike HommeyApr 13, 2016
  4. Matthieu MoyApr 14, 2016
  5. Mike HommeyApr 14, 2016
  6. Matthieu MoyApr 14, 2016
  7. Remi Galan AlfonsoApr 14, 2016
  8. Johannes SchindelinApr 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.