On 1/27/08, Patrick Schoenfeld <[EMAIL PROTECTED]> wrote: > On Sun, Jan 27, 2008 at 04:17:18PM -0200, Otavio Salvador wrote: > > --diff-cmd is the more stable way to work on this, in my opinion so it > > will always work and there's no risk to it get broken again due any > > different tool being use. > > Hmm. I'm unsure. This way debcommit depends on yet another external > utility. However: Given that diff is an essential utility, its probably > a passable solution. I could check which possibilities are supported for > the other vcses and polish my changes to make up a patch. > Any other opinions?
I think using --diff-cmd is better, as Otavio suggests. The best way would be to specify to svn to use the internal diff on the command-line, something like "svn diff --diff-cmd internal", thereby overriding any config settings. This doesn't seem possible though, as I just asked on the #svn chat on IRC and no one was able to help, so using an external diff command might be the only way. Have you checked the effects of a user setting git's color.diff option to 'always' in their .gitconfig file? I suspect the same error would occur, but I don't have a git repository with a package in it to check. Thanks, Cameron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
