On Wed, May 13, 2009 at 8:21 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote:
> Cory Sharp <cory.sharp@xxxxxxxxx> writes:
>
>> Am I doing something a little wrong or unexpected? Is there a way
>> around this squash conflict behavior? This doesn't seem to happen
>> with plain merge without squash.
>
> Of course. That's the whole point of recording a merge as a merge.
>
$ git help merge
--squash
Produce the working tree and index state as if a real merge
happened. ... This allows you to create a
single commit on top of the current branch whose effect is
the same as merging another branch.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html