-
Notifications
You must be signed in to change notification settings - Fork 16
Commit
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -172,9 +172,11 @@ Table of Contents | |
|
||
When range patches are transmitted outside of HTTP session, a | ||
stand-alone range patch format can be used. For example, in this | ||
format it can be stored in a file. The format reuses structure from | ||
HTTP and consists of headers separated from the patch body by an | ||
empty line. Only Content-Range header is required. Example: | ||
format a patch can be stored in a file, send to a mailing list, or a | ||
code version control system can display the patch in the range patch | ||
format. The format reuses structure from HTTP and consists of | ||
headers separated from the patch body by an empty line. Only | ||
Content-Range header is required. Example: | ||
|
||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
mitar
Author
Member
|
||
Content-Range: json /foo/bar/3/baz | ||
|
||
|
I'm still not sold on this part, but that's ok.
One issue is that you can't replace multiple ranges in a single file with this format. That makes it a poor substitute for a universal diff, because you need a new file for each edit you made to a file.