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

Re: Generating patches/Cherry Picking for a large number of commits

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 28, 2009, 22:35 UTC
Message-ID
<7v1vmvh8hs.fsf@alter.siamese.dyndns.org>
In-Reply-To
<m3k50nllt6.fsf@localhost.localdomain>
Jakub Narebski <jnareb@gmail.com> writes:
> git-format-patch | git-am pipeline has to work correctly, as it
> originally was the way (modulo extra options) git-rebase was
> implemented.  So yes, "git am <dir>" should understand and apply in
> correct order result of "git format-patch -o <dir> <revspec>".

You are not making any sense. rebase is done using --stdout and does not rely on the intermediate files nor ordering of their names.

Previous: Jakub NarebskiNext: Jeff King
Message 5 of 7 in “Generating patches/Cherry Picking for a large number of commits”
  1. AlydisAug 28, 2009
  2. Jeff KingAug 28, 2009
  3. AlydisAug 28, 2009
  4. Jakub NarebskiAug 28, 2009
  5. Junio C HamanoAug 28, 2009
  6. Jeff KingAug 28, 2009
  7. Junio C HamanoAug 28, 2009

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.