From: Martin Langhoff <martin.langhoff@gmail.com>
To: GIT <git@vger.kernel.org>
Subject: cogito and merging in steps.
Date: Tue, 23 Aug 2005 18:29:46 +1200 [thread overview]
Message-ID: <46a038f9050822232961140d4b@mail.gmail.com> (raw)
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 reply other threads:[~2005-08-23 6:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 6:29 Martin Langhoff [this message]
2005-09-12 0:11 ` cogito and merging in steps Petr Baudis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46a038f9050822232961140d4b@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).