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

cogito and merging in steps.

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Aug 23, 2005, 06:29 UTC
Message-ID
<46a038f9050822232961140d4b@mail.gmail.com>
Is there any way to merge patches "selectively"? 
I have found that if I do 
   cg-pull
   cg-log -r master:origin
I can review the commits that will be merged if I do cg-update. 

Say I do cg-update, it brings a lot of commits and there is a messy conflict. I immediately can narrow down on which commit I am merging it is that has a conflict.

With this info, it'd be interesting to be able to merge not to the tip of the head (head of the head? =- bah, tip of the branch! :) but to an earlier commit, so I can resolve the conflict with a more specific commit.

Say I am merging a series of 10 commits that happened in the shared repo to the project while I worked disconnected (and did lots of local commits). The first 8 commits merge cleanly, the 9th is an ugly conflict I have to resolve, and the 10th is clean and unrelated.

I want to be able to 
 - cg-update
 - oops! this is a mess! review with cg-log -r master:origin
 - aha! Here is the conflict in the 9th commit from MacFroz, fire off
email / open irc session
 - in the meantime, reset the working copy and merge the 8 clean ones
with something like: cg-restore ; cg-update origin^^^ ; cg-commit
 - cg-update origin^ ; emacs file-with-conflict.c ; cg-commit 
 - cg-update # bring in the last pending commit from origin. 

How can I achieve the cg-update <somepointinthebranch> ; cg-commit ? I mean, without faking a head with

  echo <somepointinthebranch> > .git/refs/heads/temphead 
cheers,

martin cheers,

martin
Next: Petr Baudis
Message 1 of 2 in “cogito and merging in steps.”
  1. Martin LanghoffAug 23, 2005
  2. Petr BaudisSep 12, 2005

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.