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

Re: How to pull a single changeset from a child branch into a parent branch?

From
BGBen Greear <greearb@candelatech.com>
Date
Feb 10, 2006, 21:16 UTC
Message-ID
<43ED02A5.6030500@candelatech.com>
In-Reply-To
<7vzmkzyfhh.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
Show 39 quoted lines
> Ben Greear <greearb@candelatech.com> writes:
> 
> 
>>I have a linux-2.6 repo with two branches off of 2.6.13.
>>
>>One branch (ben_v13) has just my own changes.
>>A second branch (work_v13) has the 2.6.13.5 patch, and I've also pulled
>>ben_v13 into it.
> 
> 
>                      "2.6.13.5"
>          o---o---o---o
>         /             \ "work_v13"
>     ---o "2.6.13"  .---*
>         \         /
>          o---o---o
>                  "ben_v13"
> 
> 	'o' are commits, '*' is a merge.
> 
> 
>>Now, I made a small change to work_v13,
> 
> 
>                      "2.6.13.5"
>          o---o---o---o
>         /             \   "work_v13"
>     ---o "2.6.13"  .---*---x
>         \         /        (new change)
>          o---o---o
>                  "ben_v13"
> 
> 
>>... and I'd like to pull only
>>that changeset into ben_v13.  Is there a way to do that w/out
>>having to export and apply a patch?
> 
> 
> I would have done things differently.

Yeah, the main problem is that I test in the combined tree and forgot to change to the ben_v13 tree before making my changes...

I'll try out the cherry-pick option..and if that doesn't work, I'll just manually patch the changes into the ben_v13 tree.

Thanks, Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com
Previous: Junio C Hamano
Message 3 of 3 in “How to pull a single changeset from a child branch into a parent branch?”
  1. Ben GreearFeb 10, 2006
  2. Junio C HamanoFeb 10, 2006
  3. Ben GreearFeb 10, 2006

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.