Skip to content

Commit

Permalink
revert/cherry-pick: use aggressive merge.
Browse files Browse the repository at this point in the history
After doing an in-index 3-way merge, we always do the stock
"merge-index merge-one-file" without doing anything fancy;
use of --aggressive helps performance quite a bit.

Signed-off-by: Junio C Hamano <junkio@cox.net>
  • Loading branch information
Linus Torvalds authored and Junio C Hamano committed May 10, 2006
1 parent 28cc4ab commit d180285
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion git-revert.sh
Original file line number Diff line number Diff line change
Expand Up @@ -137,7 +137,7 @@ esac >.msg
# $prev and $commit on top of us (when cherry-picking or replaying).

echo >&2 "First trying simple merge strategy to $me."
git-read-tree -m -u $base $head $next &&
git-read-tree -m -u --aggressive $base $head $next &&
result=$(git-write-tree 2>/dev/null) || {
echo >&2 "Simple $me fails; trying Automatic $me."
git-merge-index -o git-merge-one-file -a || {
Expand Down

0 comments on commit d180285

Please sign in to comment.