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

Re: one half of a rebase

From
Alex Riesen <raa.lkml@gmail.com>
Date
Sep 11, 2009, 21:10 UTC
Message-ID
<81b0412b0909111410k3f3ebfaco393bb37ff5a6b5c1@mail.gmail.com>
In-Reply-To
<7f9d599f0909111025q42e3cdc6vba602b84c1d81215@mail.gmail.com>
On Fri, Sep 11, 2009 at 19:25, Geoffrey Irving <irving@naml.us> wrote:
Show 8 quoted lines
> If I could do (2) as a separate operation, it would look something like
>
>    git cherry-pick-all topic
>
> which is simpler and faster since it avoids switching files back and
> forth (master to topic and back).  Is there a robust way to achieve
> the cherry-pick-all semantics with current commands?  If not, how
> difficult would it be to partition rebase accordingly?
I have this in my .bashrc:
$ gcp3 ()
{
    git format-patch -k --stdout --full-index "$@" | git am -k -3 --binary
}
Then, while on master branch:
$ gcp3 master..topic
Previous: Matthieu MoyNext: Geoffrey Irving
Message 3 of 5 in “one half of a rebase”
  1. Geoffrey IrvingSep 11, 2009
  2. Matthieu MoySep 11, 2009
  3. Alex RiesenSep 11, 2009
  4. Geoffrey IrvingSep 12, 2009
  5. Paolo BonziniSep 12, 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.