From: Richard Hartmann <richih.mailinglist@gmail.com>
Date: Thu, 16 Oct 2008 22:10:55 GMT
Subject: commiting while the current version is in conflict
Message-ID: <2d460de70810161510ha220593g4615a55b2c3e3b25@mail.gmail.com>

Hi all,

I fooled around with git a liitle bit and noticed something
rather strange. I merged two branches, creating a conflict
on purpose. When I then did a

 git commit -a

all changes were submitted. Of course, I now have a
file with the conflict markers inlined in my repository. Not
a good thing, imo. Is there a way to make git block all
conflicting versions?

Also, I would be interested in the design decissions
behind the current behaviour. Any pointers?


Thanks,
Richard