comparison mercurial/patch.py @ 23924:0db6810e84e8 stable

diff: use binary diff when copy source is binary

When a binary source has been copied or renamed into a non-binary
file, we don't check whether the copy source was binary. There is a
code comment explaining that a git mode will be forced anyway in order
to capture the copy record (i.e. losedatafn() will be called). This is
true, but forcing git mode is not the only effect binary files have:
when git mode was already requested, we use the binary-ness to tell us
whether to use a regular unified diff or a git binary diff. The user
sees this as a "Binary file $file has changed" instead of the binary

23923:ab6fd3205dad

                else:
                    if opts.git:
                        header.append('new file mode %s\n' % mode)
                    elif ctx2.flags(f):
                        losedatafn(f)
                # In theory, if tn was copied or renamed we should check
                # if the source is binary too but the copy record already
                # forces git mode.
                if util.binary(tn):
                    if opts.git:
                        binarydiff = True
                    else:
                        losedatafn(f)
                if not opts.git and not tn:

23924:0db6810e84e8

                else:
                    if opts.git:
                        header.append('new file mode %s\n' % mode)
                    elif ctx2.flags(f):
                        losedatafn(f)
                if util.binary(to) or util.binary(tn):
                    if opts.git:
                        binarydiff = True
                    else:
                        losedatafn(f)
                if not opts.git and not tn: