Re: [BUG] (git commit --patch --message $MESSAGE) disallows hunk editing

2014-09-29 Thread Max Nanasy
Max Nanasy 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 u

[PATCH v2] diff.c: diff.renamelimit => diff.renameLimit in message

2013-03-21 Thread Max Nanasy
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-of

Re: git merge behavior

2013-03-21 Thread Max Nanasy
Yann Droneaud 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 override

[PATCH] diff.c: diff.renamelimit => diff.renameLimit in message

2013-03-21 Thread Max Nanasy
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-b

[BUG] (git commit --patch --message $MESSAGE) disallows hunk editing

2012-10-22 Thread Max Nanasy
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 une