From: Davide Libenzi <davidel@xmailserver.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: your mail
Date: Wed, 22 Nov 2006 12:16:58 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0611221208430.27569@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0611212316080.26827@wbgn013.biozentrum.uni-wuerzburg.de>
On Tue, 21 Nov 2006, Johannes Schindelin wrote:
> [PATCH] xdiff: add xdl_merge()
>
> This new function implements the functionality of RCS merge, but
> in-memory. It returns < 0 on error, otherwise the number of conflicts.
>
> Finding the conflicting lines can be a very expensive task. You can
> control the eagerness of this algorithm:
>
> - a level value of 0 means that all overlapping changes are treated
> as conflicts,
> - a value of 1 means that if the overlapping changes are identical,
> it is not treated as a conflict.
> - If you set level to 2, overlapping changes will be analyzed, so that
> almost identical changes will not result in huge conflicts. Rather,
> only the conflicting lines will be shown inside conflict markers.
>
> With each increasing level, the algorithm gets slower, but more accurate.
> Note that the code for level 2 depends on the simple definition of
> mmfile_t specific to git, and therefore it will be harder to port that
> to LibXDiff.
Johannes, at the moment I'm chased by a huge storm of never ending emails,
so I won't be able to follow up this one soon. A smart 3-way merge is in
my plans for LibXDiff though.
There is quite some nice code around, that does pretty smart tricks and
goes down to resolve sub-hunk non-trivial conflicts. You may want to take
a look at that code too.
- Davide
next prev parent reply other threads:[~2006-11-22 20:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 22:24 (unknown) Johannes Schindelin
2006-11-21 23:15 ` [PATCH] xdiff: add xdl_merge() (was: (unknown)) Jakub Narebski
2006-11-22 9:29 ` Johannes Schindelin
2006-11-22 19:58 ` [PATCH] xdiff: add xdl_merge() Ramsay Jones
2006-11-22 20:16 ` Davide Libenzi [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-24 0:38 shejan shuza
2020-06-24 1:31 ` your mail brian m. carlson
2019-11-20 3:49 Han-Wen Nienhuys
2019-11-20 5:30 ` your mail Taylor Blau
2019-11-20 8:05 ` Christian Couder
2019-07-11 20:11 Robert Morgan
2019-07-11 20:18 ` your mail Kevin Daudt
2019-07-11 20:25 ` Robert Morgan
2019-01-25 9:47 Furkan DURUL
2019-01-25 11:27 ` your mail Kevin Daudt
2017-06-22 9:50 Jessie Hernandez
2017-06-22 12:48 ` your mail Simon Ruderich
2017-06-22 13:35 ` AW: " Patrick Lehmann
2017-06-22 13:47 ` Simon Ruderich
2017-06-22 13:55 ` AW: " Patrick Lehmann
2017-06-22 20:46 ` Simon Ruderich
2017-06-22 21:35 ` Junio C Hamano
2017-06-22 21:58 ` Ævar Arnfjörð Bjarmason
2017-06-22 22:14 ` Junio C Hamano
2017-06-22 23:21 ` Jeff King
2017-06-23 5:23 ` Junio C Hamano
2017-06-23 16:53 ` Jeff King
2017-06-23 18:44 ` Junio C Hamano
2017-06-23 6:58 ` demerphq
2016-04-11 19:04 (unknown), miwilliams
2016-04-11 19:13 ` your mail Jeff King
2013-05-17 18:02 (unknown), ASHISH VERMA
2013-05-21 13:13 ` your mail Magnus Bäck
2012-05-06 14:17 (unknown), Bruce Zu
2012-05-06 17:04 ` your mail Marcus Karlsson
2008-08-13 14:54 (unknown), aneesh.kumar
2008-08-13 15:16 ` your mail Aneesh Kumar K.V
2007-12-05 19:00 [PATCH 0/6] builtin-remote Johannes Schindelin
2007-12-05 19:00 ` (unknown) Johannes Schindelin
2007-12-05 19:01 ` your mail Johannes Schindelin
2007-10-13 4:01 (unknown), Michael Witten
2007-10-13 4:07 ` your mail Jeff King
2006-10-20 14:24 (unknown) andyparkins
2006-10-20 14:42 ` your mail Johannes Schindelin
[not found] <C8DBC54F2A9BAD4FA7F445CC7ADD963B0232474F@sslmexchange1.paymentech.us>
2006-09-26 19:56 ` Linus Torvalds
2006-05-21 23:53 (unknown) J. Bruce Fields
2006-05-21 23:55 ` your mail J. Bruce Fields
2006-05-22 0:16 ` Junio C Hamano
2006-05-22 1:33 ` J. Bruce Fields
2005-10-05 6:10 (unknown), Willem Swart
2005-10-06 10:52 ` your mail Elfyn McBratney
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0611221208430.27569@alien.or.mcafeemobile.com \
--to=davidel@xmailserver.org \
--cc=Johannes.Schindelin@gmx.de \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).