Summary: | Diff with New Files | ||
---|---|---|---|
Product: | [Developer tools] kdevplatform | Reporter: | David E. Narvaez <david.narvaez> |
Component: | git | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | aleixpol |
Priority: | NOR | ||
Version: | git master | ||
Target Milestone: | 1.2.3 | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
David E. Narvaez
2011-10-04 21:14:24 UTC
Why do you want the new files on the diff? (In reply to comment #1) > Why do you want the new files on the diff? My use case? As a KDE Developer, I need the new files I create when I implement new features to be submitted in the review patch. In general, I think you can always find use cases where you need the new files included in the patch and use cases where you don't, so it's just a matter of which case do we want to support, or change the UI to opt in/out the new files. instead of "git diff HEAD" you probably want "git diff --cached" no? Git commit 91cb3d32588b7f5a3d866805e4583caa464c81cd by Aleix Pol. Committed on 05/10/2011 at 02:35. Pushed by apol into branch 'master'. In case we're comparing BASE to WORKING, add the staged changes as well. BUG: 283352 M +12 -3 plugins/git/gitplugin.cpp M +1 -2 plugins/git/gitplugin.h http://commits.kde.org/kdevplatform/91cb3d32588b7f5a3d866805e4583caa464c81cd |