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

Re: Performance Issues with Git Rebase

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 13, 2014, 17:25 UTC
Message-ID
<xmqqlhoj51bi.fsf@gitster.dls.corp.google.com>
In-Reply-To
<B82B660D4887C042850326C2BC65FE035D56CA14@G4W3227.americas.hpqcorp.net>
"Crabtree, Andrew" <andrew.crabtree@hp.com> writes:
> I'm getting the same output with both the triple and double dot for my
> specific case, but I have no idea if that change makes sense for all
> cases or not.  Any guidance?

The difference only matters if any of your 4 patches have been sent to your upstream and accepted and appear among the 4665 changes they have.

The --cherry-pick option is about cross checking the combinations of 4 x 4665 and filter out matching ones (if any).

Previous: Crabtree, AndrewNext: Crabtree, Andrew
Message 2 of 3 in “Performance Issues with Git Rebase”
  1. Crabtree, AndrewOct 12, 2014
  2. Junio C HamanoOct 13, 2014
  3. Crabtree, AndrewOct 13, 2014

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.