Git development
 help / color / mirror / Atom feed
From: Nanako Shiraishi <nanako3@lavabit.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nelson Elhage <nelhage@MIT.EDU>, git@vger.kernel.org
Subject: Re: [PATCH] Always output a trailing space conflicted merge markers.
Date: Wed, 01 Jul 2009 12:42:20 +0900	[thread overview]
Message-ID: <20090701124220.6117@nanako3.lavabit.com> (raw)
In-Reply-To: <7v1vp15ppi.fsf@alter.siamese.dyndns.org>

Quoting Junio C Hamano <gitster@pobox.com>:

> Nelson Elhage <nelhage@MIT.EDU> writes:
>
>> Some tools, such as emacs' smerge-mode, except that diff3-style merge
>> conflict markers always include a trailing space (and optional
>> description) after the marker, and so fail to correctly detect
>> git's (notably the '|||||||' base marker, for which git never outputs a
>> trailing space).
>>
>> (See http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=3553
>> for the emacs issue)
>>
>> Signed-off-by: Nelson Elhage <nelhage@mit.edu>
>> ---
>>  xdiff/xmerge.c |   11 ++++++++---
>>  1 files changed, 8 insertions(+), 3 deletions(-)
>
> Thanks, but I think you also need to update the test scripts.
>
> Don't you want some new tests to protect this from getting broken
> in the future by other people yourself, too?

I don't know what future breakages Nelson wants to protect his code from, but this change breaks the test for union merge in t6026-merge-attr.sh.

It isn't that the test script expects no space after the conflict marker, but with Nelson's patch, the union merge no longer works.

I request this patch to be dropped.

-- 
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/

      parent reply	other threads:[~2009-07-01  3:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30  0:41 [PATCH] Always output a trailing space conflicted merge markers Nelson Elhage
2009-06-30 22:20 ` Junio C Hamano
2009-07-01  2:01   ` Junio C Hamano
2009-07-01  3:42   ` Nanako Shiraishi [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=20090701124220.6117@nanako3.lavabit.com \
    --to=nanako3@lavabit.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nelhage@MIT.EDU \
    /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