Git development
 help / color / mirror / Atom feed
From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: git@vger.kernel.org
Subject: Cogito: Merge failure when new remote has been added locally
Date: Thu, 13 Oct 2005 22:06:39 -0300	[thread overview]
Message-ID: <200510140106.j9E16dfn017346@inti.inf.utfsm.cl> (raw)

I've set up an example project to play around with cogito/git. To simulate
patches flowing back and forth I set up several repositories, which I edit
independently. In this I run into trouble with a reasonable scenario:

 A creates a project, and publishes it

 B gets A's version, updates his version, and ships a patch (which creates
   stack.h) to A

 A merges in B's changes, and fixes a typo in stack.h

 B tries to update from A via cg-update, the merge fails because there is a
   local stack.h (which is different than the remote one). The resulting
   message is less than helpful.

A script showing the problem follows:

   mkdir tst1
   cd tst1
   echo "Initial" | cg-init
   
   cd ..
   cg-clone tst1 tst2

   cd tst2
   echo 'Hello!' > greet
   cg-add greet
   cg-commit -m "Add greet"

   cd ../tst1
   echo 'Hi there!' > greet
   cg-add greet
   cg-commit -m "Add greet"

   cd ../tst2
   cg-update

This gives:


     MERGE ERROR: : Not handling case  ->  ->

            Conflicts during merge. Do cg-commit after resolving them.

And there is nothing marked to fix by hand. cg-diff returns an empty
difference in greet.
-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513

                 reply	other threads:[~2005-10-14  1:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200510140106.j9E16dfn017346@inti.inf.utfsm.cl \
    --to=vonbrand@inf.utfsm.cl \
    --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