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

Re: rename detection limit checking, cherry picking, and git am -3

From
Karl Hasselström <kha@treskal.com>
Date
Sep 17, 2007, 09:58 UTC
Message-ID
<20070917095829.GD8657@diana.vm.bytemark.co.uk>
In-Reply-To
<7v3axd5325.fsf@gitster.siamese.dyndns.org>
On 2007-09-16 21:27:46 -0700, Junio C Hamano wrote:
Show 5 quoted lines
> I think it would make sense to do the consolidated backend for
> rebase, revert, cherry-pick and am (I have been tentatively calling
> this "git replay") primarily based on the "patch with fallback to
> 3-way" like format-patch piped to "am -3", with an option to do
> merge-recursive.
I guess such a backend would be useful for StGit as well.
-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Previous: Junio C HamanoNext: Mark Levedahl
Message 4 of 5 in “rename detection limit checking, cherry picking, and git am -3”
  1. Mark LevedahlSep 17, 2007
  2. Shawn O. PearceSep 17, 2007
  3. Junio C HamanoSep 17, 2007
  4. Karl HasselströmSep 17, 2007
  5. Mark LevedahlSep 18, 2007

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.