Git development
 help / color / mirror / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: Git Mailing List <git@vger.kernel.org>,
	Petr Baudis <pasky@ucw.cz>, Junio C Hamano <junkio@cox.net>
Subject: Re: cg-merge should use git-merge
Date: Thu, 20 Oct 2005 20:04:52 +1300	[thread overview]
Message-ID: <46a038f90510200004l67e2d19kf8e9a4c6190f44f@mail.gmail.com> (raw)
In-Reply-To: <46a038f90510190421l50b2c12k495db23b62015782@mail.gmail.com>

On 10/20/05, Martin Langhoff <martin.langhoff@gmail.com> wrote:
> After using git-merge a few times by hand to test-drive the new merge
> drivers, I'm sold on the idea, and I 'd like to have cg-merge use
> git-merge directly.

I started drafting a 5-minute proof-of-concept, and then it struck me:
cg users aren't aware of the index. This is really important when you
are merging and have to resolve a conflict over a dirty tree. git
users know that the "clean" part of the merge is in the index, and
they have to resolve a couple of files in their checkout, and update
the index for those only before calling git-write-tree &
git-commit-tree.

Cogito users don't know about this magic at all, which is a bit of a
problem. I can refuse to run cg-merge on a dirty tree to make things
simpler, but that's cheating ;-)

tagging "for later"...

cheers,


martin

      reply	other threads:[~2005-10-20  7:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46a038f90510161644l35119401rdc05c081506ae715@mail.gmail.com>
     [not found] ` <46a038f90510161744m7e95303eu8a9942363ffc58a6@mail.gmail.com>
2005-10-17  8:31   ` cg-merge should use git-merge Junio C Hamano
     [not found]     ` <46a038f90510170203ndee2b2bi913b62014614f68e@mail.gmail.com>
2005-10-17  9:26       ` Junio C Hamano
2005-10-19 11:21 ` Fwd: " Martin Langhoff
2005-10-20  7:04   ` Martin Langhoff [this message]

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=46a038f90510200004l67e2d19kf8e9a4c6190f44f@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=pasky@ucw.cz \
    /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