| commit | f825972c38ba5a8e0309a552b401ad55aeaaaf36 | |
| author | Felipe Contreras <felipe.contreras@gmail.com> | |
| Sat, 27 Apr 2013 20:10:03 +0000 (27 15:10 -0500) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Sat, 27 Apr 2013 21:32:29 +0000 (27 14:32 -0700) | ||
| tree | c6ef652adf7665ca7ec2217b16f8fdfd0378a819 | treesnapshot (tar.gz zip) |
| parent | 0afe8e9e98b0b066105e03476f7c8f4c14bc1c15 | commitdiff |
completion: refactor diff_index wrappers
At the end of the day what we really need is to find out the files that
have been staged, or modified, because those files are the ones that
make sense to pass as arguments to 'git commit'.
We need diff-index to find those out, since 'git ls-files' doesn't do
that.
But we don't need wrappers and wrappers basically identical to the ones
used for 'git ls-files', when we can pretend it receives a --committable
option that would return what we need.
That way, we can remove a bunch of code without any functional changes.
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
At the end of the day what we really need is to find out the files that
have been staged, or modified, because those files are the ones that
make sense to pass as arguments to 'git commit'.
We need diff-index to find those out, since 'git ls-files' doesn't do
that.
But we don't need wrappers and wrappers basically identical to the ones
used for 'git ls-files', when we can pretend it receives a --committable
option that would return what we need.
That way, we can remove a bunch of code without any functional changes.
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| contrib/completion/git-completion.bash | diffblobblamehistory |