Merge branch 'master' into next

* master:
  Update draft release notes to 1.7.1
  rebase -i: make post-rewrite work for 'edit'
  Prepare for 1.7.0.4
This commit is contained in:
Junio C Hamano
2010-03-28 21:59:34 -07:00
4 changed files with 48 additions and 11 deletions

View File

@@ -0,0 +1,19 @@
Git v1.7.0.4 Release Notes (draft)
==================================
Fixes since v1.7.0.3
--------------------
* Color values given to "color.<cmd>.<slot>" configuration can now have
more than one attributes (e.g. "bold ul").
* "git add -u nonexistent-path" did not complain.
* "git apply --whitespace=fix" didn't work well when an early patch in
a patch series adds trailing blank lines and a later one depended on
such a block of blank lines at the end.
* "git fast-export" didn't check error status and stop when marks file
cannot be opened.
And other minor fixes and documentation updates.

View File

@@ -7,19 +7,14 @@ Updates since v1.7.0
* Some commands (e.g. svn and http interfaces) that interactively ask
password can be told to use an external program given via GIT_ASKPASS.
* Color values given to "color.<cmd>.<slot>" configuration can now have
more than one attributes (e.g. "bold ul").
* "git apply --whitespace=fix" didn't work well when an early patch in
a patch series adds trailing blank lines and a later one depended on
such a block of blank lines at the end.
* "git am" learned "--keep-cr" option to handle inputs that are
mixture of changes to files with and without CRLF line endings.
* "git cvsimport" learned -R option to leave revision mapping between
CVS revisions and resulting git commits.
* "git diff --submodule" notices and descries dirty submodules.
* "git for-each-ref" learned %(symref), %(symref:short) and %(flag)
tokens.
@@ -36,11 +31,15 @@ Updates since v1.7.0
* "git grep" learned to paint filename and line-number in colors.
* "git log -p --first-parent -m" shows one-parent diff for merge
commits, instead of showing combined diff.
* "git merge-file" learned to use custom conflict marker size and also use
the "union merge" behaviour.
* "git notes" command has been rewritten in C and learned quite a
many commands.
many commands and features to help you carry notes forward across
rebases and amends.
* "git request-pull" identifies the commit the request is relative to in
a more readable way.
@@ -49,6 +48,8 @@ Updates since v1.7.0
near the tip while preserving your local changes in a way similar
to how "git checkout branch" does.
* "git status" notices and descries dirty submodules.
* "git svn" should work better when interacting with repositories
with CRLF line endings.
@@ -66,5 +67,5 @@ release, unless otherwise noted.
---
exec >/var/tmp/1
echo O=$(git describe)
O=v1.7.0.2-323-g0d0925c
O=v1.7.0.3-310-g99f5b08
git shortlog --no-merges ^maint $O..

View File

@@ -475,7 +475,7 @@ do_next () {
mark_action_done
pick_one $sha1 ||
die_with_patch $sha1 "Could not apply $sha1... $rest"
echo "$1" > "$DOTEST"/stopped-sha
echo "$sha1" > "$DOTEST"/stopped-sha
make_patch $sha1
git rev-parse --verify HEAD > "$AMEND"
warn "Stopped at $sha1... $rest"
@@ -723,9 +723,10 @@ first and then run 'git rebase --continue' again."
test -n "$amend" && git reset --soft $amend
die "Could not commit staged changes."
}
record_in_rewritten "$(cat "$DOTEST"/stopped-sha)"
fi
record_in_rewritten "$(cat "$DOTEST"/stopped-sha)"
require_clean_work_tree
do_rest
;;

View File

@@ -180,4 +180,20 @@ EOF
verify_hook_input
'
test_expect_success 'git rebase -i (double edit)' '
git reset --hard D &&
clear_hook_input &&
FAKE_LINES="edit 1 edit 2" git rebase -i B &&
git rebase --continue &&
echo something > foo &&
git add foo &&
git rebase --continue &&
echo rebase >expected.args &&
cat >expected.data <<EOF &&
$(git rev-parse C) $(git rev-parse HEAD^)
$(git rev-parse D) $(git rev-parse HEAD)
EOF
verify_hook_input
'
test_done