Re: xxdiff as a visual diff tool (shameless plug)

[Martin Blais]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 22 March 2002 16:44, Pavel Machek wrote:
> Hi!
> > that seems more like a patch problem/improvement request. i wouldn't do
> > the patch myself... however, with the rejected hunks problem, i wonder if
> > it is at all possible to avoid implementing patch functionality in the
> > diffing tool itself.
>
> Question is how to do it in patch. Even one *long line* can be too
> much, and then your horizontal highlight would come very handy.

actually, thinking more about it, having to use patch is not really a problem 
for the BK use case discussed on this list, as BK most likely can provide the 
file on the main branch and the common ancestor between the developer's 
branch and the main branch. one then just needs to spawn a 3-way xxdiff on 
those three files (with automatic selection of non-conflictual hunks). 
that's what i do with Clearcase, where all the file versions are available 
directly in the filesystem. CVS however, requires that i first fetch the file 
to a temporary copy and there is no way to figure out the common ancestor 
where the last update to the main branch occured (unless you hack it into a 
tag or something).

my point is, if you're using scm, you don't need to use patches at all, so 
there is no real need for a tool to help "wiggle patches in", in that 
context.
-----BEGIN PGP SIGNATURE-----
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjyc6coACgkQq2PmC9F3Xx3LMACeJbrnBgPsFxSGuXlL8PdCdlmm
z2wAn2qNiFC6sgpz4yQZKMGV1DzIeayx
=rB+O
-----END PGP SIGNATURE-----