Skip to content

Fix diff patch parsing #412

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Apr 19, 2016
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update changelog
  • Loading branch information
nvie committed Apr 19, 2016
commit 55d40df99085036ed265fbc6d24d90fbb1a24f95
20 changes: 17 additions & 3 deletions doc/source/changes.rst
Original file line number Diff line number Diff line change
Expand Up @@ -5,9 +5,23 @@ Changelog
1.0.3 - Fixes
=============

* `Commit.diff()` now supports diffing the root commit via `Commit.diff(NULL_TREE)`.
* `Repo.blame()` now respects `incremental=True`, supporting incremental blames. Incremental blames are slightly faster since they don't include the file's contents in them.
* IMPORTANT: This release drops support for python 2.6, which is officially deprecated by the python maintainers.
* `Commit.diff()` now supports diffing the root commit via
`Commit.diff(NULL_TREE)`.
* `Repo.blame()` now respects `incremental=True`, supporting incremental
blames. Incremental blames are slightly faster since they don't include
the file's contents in them.
* Fix: `Diff` objects created with patch output will now have their
`a_path` and `b_path` properties parsed out correctly. Previously, some
values may have been populated incorrectly when a file was added or
deleted.
* IMPORTANT: This release drops support for python 2.6, which is
officially deprecated by the python maintainers.
* CRITICAL: `Diff` objects created with patch output will now not carry
the --- and +++ header lines anymore. All diffs now start with the
@@ header line directly. Users that rely on the old behaviour can now
(reliably) read this information from the a_path and b_path properties
without having to parse these lines manually.


1.0.2 - Fixes
=============
Expand Down