summaryrefslogtreecommitdiff
path: root/t/t9142-git-svn-shallow-clone.sh
diff options
context:
space:
mode:
authorLibravatar Stephen Haberman <stephen@exigencecorp.com>2013-08-12 22:43:42 -0500
committerLibravatar Junio C Hamano <gitster@pobox.com>2013-09-04 12:45:48 -0700
commit66713ef3b00933755cdeff1ae823dda7b5843640 (patch)
treea6cd1fc40f748c761efb831cf555bab21628c47a /t/t9142-git-svn-shallow-clone.sh
parentMerge branch 'maint' (diff)
downloadtgif-66713ef3b00933755cdeff1ae823dda7b5843640.tar.xz
pull: allow pull to preserve merges when rebasing
If a user is working on master, and has merged in their feature branch, but now has to "git pull" because master moved, with pull.rebase their feature branch will be flattened into master. This is because "git pull" currently does not know about rebase's preserve merges flag, which would avoid this behavior, as it would instead replay just the merge commit of the feature branch onto the new master, and not replay each individual commit in the feature branch. Add a --rebase=preserve option, which will pass along --preserve-merges to rebase. Also add 'preserve' to the allowed values for the pull.rebase config setting. Signed-off-by: Stephen Haberman <stephen@exigencecorp.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t9142-git-svn-shallow-clone.sh')
0 files changed, 0 insertions, 0 deletions