-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* maint: Prepare draft release notes to 1.7.4.2 gitweb: highlight: replace tabs with spaces make_absolute_path: return the input path if it points to our buffer valgrind: ignore SSE-based strlen invalid reads diff --submodule: split into bite-sized pieces cherry: split off function to print output lines branch: split off function that writes tracking info and commit subject standardize brace placement in struct definitions compat: make gcc bswap an inline function enums: omit trailing comma for portability Conflicts: RelNotes
- Loading branch information
Showing
27 changed files
with
215 additions
and
178 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
Git v1.7.4.2 Release Notes | ||
========================== | ||
|
||
Fixes since v1.7.4.1 | ||
-------------------- | ||
|
||
* Many documentation updates to match "git cmd -h" output and the | ||
git-cmd manual page. | ||
|
||
* "git clone /no/such/path" did not fail correctly. | ||
|
||
* "git commit" did not correctly error out when the user asked to use a | ||
non existent file as the commit message template. | ||
|
||
* "git diff --stat -B" ran on binary files counted the changes in lines, | ||
which was nonsensical. | ||
|
||
* "git diff -M" opportunistically detected copies, which was not | ||
necessarily a good thing, especially when it is internally run by | ||
recursive merge. | ||
|
||
* "git difftool" didn't tell (g)vimdiff that the files it is reading are | ||
to be opened read-only. | ||
|
||
* "git merge" didn't pay attention to prepare-commit-msg hook, even | ||
though if a merge is conflicted and manually resolved, the subsequent | ||
"git commit" would have triggered the hook, which was inconsistent. | ||
|
||
* "git patch-id" (and commands like "format-patch --ignore-in-upstream" | ||
that use it as their internal logic) handled changes to files that end | ||
with incomplete lines incorrectly. | ||
|
||
* The official value to tell "git push" to push the current branch back | ||
to update the upstream branch it forked from is now called "upstream". | ||
The old name "tracking" is and will be supported. | ||
|
||
* gitweb's "highlight" interface mishandled tabs. | ||
|
||
* gitweb had a few forward-incompatible syntactic constructs and | ||
also used incorrect variable when showing the file mode in a diff. | ||
|
||
And other minor fixes and documentation updates. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -18,7 +18,7 @@ enum action { | |
CRLF_TEXT, | ||
CRLF_INPUT, | ||
CRLF_CRLF, | ||
CRLF_AUTO, | ||
CRLF_AUTO | ||
}; | ||
|
||
struct text_stat { | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.