The first one attempts to fix "git status" reporting intent-to-add files as "changes to be committed". The "new file" report is now moved to "git diff-files" aka "changes not staged for commit" instead.
I just want to check if I'm going on the right direction as core diff machinery is not really my area. I know these patches break t2203 and t4011 but from a quick glance, the tests simply rely on the old behavior, not real breakages. Nguyễn Thái Ngọc Duy (2): diff --cached: do not report i-t-a entries as "new" diff-files: mark i-t-a paths as "new" builtin/add.c | 1 + diff-lib.c | 7 +++++++ 2 files changed, 8 insertions(+) -- 2.3.0.rc1.137.g477eb31 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
