Describe normalized diff format

techtonik / python-patch

Library to parse and apply unified diffs

https://pypi.python.org/pypi/patch

106 stars 63 forks source link

Describe normalized diff format #5

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

Revise documentation on unified diff format and include diagrams for at least 
classic, svn and hg diff.

Original issue reported on code.google.com by techtonik@gmail.com on 25 Aug 2009 at 2:18

GoogleCodeExporter commented 9 years ago

Unified diff format doc describes SVN format. This format doesn't cover all 
user stories and is not extensive. Normalized patch format should get rid of 
these deficiencies.

1. Normalized diff uses only forward slashes in paths
2. All filenames in normalized diff are relative

Original comment by techtonik@gmail.com on 23 Nov 2012 at 9:41

Changed title: Describe normalized diff format
Added labels: P1, Type-Story
Removed labels: Priority-Medium, Type-Defect

GoogleCodeExporter commented 9 years ago

Unified diff about if file is patched is unreliable.

See also https://code.google.com/p/rainforce/wiki/ExtensibleChangesetFormat

Original comment by techtonik@gmail.com on 7 Jun 2013 at 3:03