all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bojan Nikolic <bojan@bnikolic.co.uk>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Chong Yidong <cyd@stupidchicken.com>,
	emacs-devel@gnu.org
Subject: Re: Merge in revno 100770
Date: Thu, 15 Jul 2010 22:37:47 +0100	[thread overview]
Message-ID: <877hkwifys.fsf@bnikolic.co.uk> (raw)
In-Reply-To: <m2hbk0u0k1.fsf@igel.home> (Andreas Schwab's message of "Thu, 15 Jul 2010 19:17:34 +0200")


Andreas Schwab <schwab@linux-m68k.org> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>> Do we know how could that happen?
>
> It looks like a wrong conflict resolution.  You can see the actual
> conflicts with
>
>   git show 036075de6587c79f9b609a68ddf4be09bd3a05ef src/fringe.c
>

Maybe there is a better way, but you can replay this situation in bzr by
itself with the following sequence of commands:

# Check-out of tree as it was just before the problematic merge. I
# assume in current working directory, the directory "trunk" contains
# the emacs trunk branch. If not replace "trunk/" by for example
# lp:emacs

bzr co -r 100769 trunk/ merge-problem-explain

# Replay the merge
cd merge-problem-explain
bzr merge  -r 99634.2.281 ../trunk/

..... other output............
Text conflict in src/fringe.c
....  other output ..........

If you look at the conflict t is easy to see how it can have been
resolved incorrectly. 

A suggestion related to this:

I would recommend running merge with the "--show-base" option (if this
isn't what you do anyway). In this the conflict would have been
displayed as:

,----
| <<<<<<< TREE
| 	left = LEFT_FRINGE (3, Qbottom, row->ends_at_zv_p);
|       else if ((!row->reversed_p && MATRIX_ROW_CONTINUATION_LINE_P (row))
| 	       || (row->reversed_p && row->continued_p))
| ||||||| BASE-REVISION
| 	left = LEFT_FRINGE (3, Qbottom, row->ends_at_zv_p);
|       else if (MATRIX_ROW_CONTINUATION_LINE_P (row))
| =======
| 	{
| 	  left = LEFT_FRINGE (3, Qbottom, bot_row_ends_at_zv_p);
| 	  if (bot_ind_max_y >= 0)
| 	    left_offset = bot_ind_max_y - (row->y + row->visible_height);
| 	}
|       else if (MATRIX_ROW_CONTINUATION_LINE_P (row))
| >>>>>>> MERGE-SOURCE
`----

making it rather easier to understand the conflict.

Best,
Bojan


-- 
Bojan Nikolic          ||          http://www.bnikolic.co.uk



      reply	other threads:[~2010-07-15 21:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-15 16:38 Merge in revno 100770 Eli Zaretskii
2010-07-15 17:17 ` Andreas Schwab
2010-07-15 21:37   ` Bojan Nikolic [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=877hkwifys.fsf@bnikolic.co.uk \
    --to=bojan@bnikolic.co.uk \
    --cc=cyd@stupidchicken.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.