Re: [PATCH 2/2] diffcore-rename: avoid processing duplicate destinations

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jeff King <peff@xxxxxxxx> writes:

> Like I mentioned before, I'm OK with not checking the actual diff output
> in the test. It's not like it was planned, and is just what diff_tree()
> happens to produce.  It does make sense, though....

When the topic is on processing broken input, I do not think "It
does make sense, though." is a primary point, unless the result
expected by these tests is the only possibly sane outcome
(otherwise, another equally-sensible output will be rejected as a
test failure).  So I agree that there is a possibility that we might
regret having the diff output tested here in the future when
somebody further works in the area.

But let's not worry too much about it for now.

Thanks; the solution seems reasonable.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]