Max Nanasy max.nanasy at gmail.com writes:
Tested against v1.7.12.4
Steps to reproduce:
A. cd $DIRTY_WORKING_COPY
B. git commit --patch --message $MESSAGE
C. Stage this hunk? e
Expected behavior:
After step C, the hunk opens in the user's editor
Actual behavior
In the warning message printed when rename or unmodified copy
detection was skipped due to too many files, change diff.renamelimit
to diff.renameLimit, in order to make it consistent with git
documentation, which consistently uses diff.renameLimit.
Signed-off-by: Max Nanasy max.nan...@gmail.com
Yann Droneaud ydroneaud at opteya.com writes:
3) Merge options can't be overridden.
If I modify .git/config to set a merge option, for example forcing
fast-forward merge, this option cannot be overridden on command line:
(git merge --no-ff-only --no-ff) should work. The --no-ff-only
In the warning message printed when rename or unmodified copy
detection was skipped due to too many files, change diff.renamelimit
to diff.renameLimit, in order to make it consistent with git
documentation, which consistently uses diff.renameLimit.
Signed-off-by: Max Nanasy max.nan...@gmail.com
Tested against v1.7.12.4
Steps to reproduce:
A. cd $DIRTY_WORKING_COPY
B. git commit --patch --message $MESSAGE
C. Stage this hunk? e
Expected behavior:
After step C, the hunk opens in the user's editor
Actual behavior:
After step C, the hunk is selected
5 matches
Mail list logo