From: Petr Baudis <pasky@suse.cz>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: git@vger.kernel.org
Subject: Re: Merge failure problem with cogito: How to fixup?
Date: Mon, 24 Oct 2005 00:32:40 +0200 [thread overview]
Message-ID: <20051023223240.GU30889@pasky.or.cz> (raw)
In-Reply-To: <200510231557.j9NFvptA020919@inti.inf.utfsm.cl>
Dear diary, on Sun, Oct 23, 2005 at 05:57:51PM CEST, I got a letter
where Horst von Brand <vonbrand@inf.utfsm.cl> told me that...
> When doing the following:
>
> mkdir /tmp/tst1
> cd /tmp/tst1
> echo "Initial" | cg-init
>
> cd /tmp
> cg-clone tst1 tst2
>
> cd /tmp/tst1
> echo 'Hi there!' > greet
> cg-add greet
> cg-commit -m "Add greet"
>
> cd /tmp/tst2
> echo 'Hello!' > greet
> cg-add greet
> cg-commit -m "Add greet"
>
> cg-update
>
> I get a message to the end that the merge doesn't work, and that I have to
> fix up by hand. The resulting greet file has no merge markers, plain
> "cg-diff" is useless. How am I supposed to find out what the problem is?
>
> Yes, "cg-diff -r origin:HEAD" does the trick, but...
Well, yes, that's one of the "unhandled merge cases". :-)
To fixup:
<resolve the merge somehow, probably adding greet in some form>
cg-add greet
(You should be able to cg-rm greet instead if you decide to drop the
file after all.)
This is a _trick_ and it works just because cg-add and cg-rm purely
accidentally do the right GIT commands to also resolve an index-level
merge conflict. The proper solution would be to add the proper case to
cg-Xmergefile, which should be actually pretty easy, if only someone
does it... ;-)
Ok, and cg-status should be taught about it and report "greet" somehow
as a conflict until you choose one of the versions.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
prev parent reply other threads:[~2005-10-23 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-23 15:57 Merge failure problem with cogito: How to fixup? Horst von Brand
2005-10-23 22:32 ` Petr Baudis [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=20051023223240.GU30889@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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