Skip to content

Commit

Permalink
Sync with 1.7.0.5
Browse files Browse the repository at this point in the history
  • Loading branch information
gitster committed Apr 11, 2010
2 parents fb10369 + fcd4240 commit 7b575f3
Show file tree
Hide file tree
Showing 4 changed files with 39 additions and 11 deletions.
26 changes: 26 additions & 0 deletions Documentation/RelNotes-1.7.0.5.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
Git v1.7.0.5 Release Notes
==========================

Fixes since v1.7.0.4
--------------------

* "git daemon" failed to compile on platforms without sockaddr_storage type.

* Output from "git rev-list --pretty=oneline" was unparsable when a
commit did not have any message, which is abnormal but possible in a
repository converted from foreign scm.

* "git stash show <commit-that-is-not-a-stash>" gave an error message
that was not so useful. Reworded the message to "<it> is not a
stash".

* Python scripts in contrib/ area now start with "#!/usr/bin/env python"
to honor user's PATH.

* "git imap-send" used to mistake any line that begins with "From " as a
message separator in format-patch output.

* Smart http server backend failed to report an internal server error and
infinitely looped instead after output pipe was closed.

And other minor fixes and documentation updates.
19 changes: 10 additions & 9 deletions Documentation/blame-options.txt
Original file line number Diff line number Diff line change
Expand Up @@ -79,22 +79,23 @@ of lines before or after the line given by <start>.
of the --date option at linkgit:git-log[1].

-M|<num>|::
Detect moving lines in the file as well. When a commit
moves a block of lines in a file (e.g. the original file
has A and then B, and the commit changes it to B and
then A), the traditional 'blame' algorithm typically blames
the lines that were moved up (i.e. B) to the parent and
assigns blame to the lines that were moved down (i.e. A)
to the child commit. With this option, both groups of lines
are blamed on the parent.
Detect moved or copied lines within a file. When a commit
moves or copies a block of lines (e.g. the original file
has A and then B, and the commit changes it to B and then
A), the traditional 'blame' algorithm notices only half of
the movement and typically blames the lines that were moved
up (i.e. B) to the parent and assigns blame to the lines that
were moved down (i.e. A) to the child commit. With this
option, both groups of lines are blamed on the parent by
running extra passes of inspection.
+
<num> is optional but it is the lower bound on the number of
alphanumeric characters that git must detect as moving
within a file for it to associate those lines with the parent
commit.

-C|<num>|::
In addition to `-M`, detect lines copied from other
In addition to `-M`, detect lines moved or copied from other
files that were modified in the same commit. This is
useful when you reorganize your program and move code
around across files. When this option is given twice,
Expand Down
3 changes: 2 additions & 1 deletion Documentation/git.txt
Original file line number Diff line number Diff line change
Expand Up @@ -43,9 +43,10 @@ unreleased) version of git, that is available from 'master'
branch of the `git.git` repository.
Documentation for older releases are available here:

* link:v1.7.0.4/git.html[documentation for release 1.7.0.4]
* link:v1.7.0.5/git.html[documentation for release 1.7.0.5]

* release notes for
link:RelNotes-1.7.0.5.txt[1.7.0.5],
link:RelNotes-1.7.0.4.txt[1.7.0.4],
link:RelNotes-1.7.0.3.txt[1.7.0.3],
link:RelNotes-1.7.0.2.txt[1.7.0.2],
Expand Down
2 changes: 1 addition & 1 deletion GIT-VERSION-GEN
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
#!/bin/sh

GVF=GIT-VERSION-FILE
DEF_VER=v1.7.0.4
DEF_VER=v1.7.1.rc1.GIT

LF='
'
Expand Down

0 comments on commit 7b575f3

Please sign in to comment.