delta/libgit2.git/src/diff_xdiff.h, branch ethomson/proxy github.com: libgit2/libgit2.git Make sure to always include "common.h" first 2017-07-03T08:51:48+00:00 Patrick Steinhardt ps@pks.im 2017-06-30T11:39:01+00:00 0c7f49dd4316b332f30b4ea72a657bace41e1245 Next to including several files, our "common.h" header also declares various macros which are then used throughout the project. As such, we have to make sure to always include this file first in all implementation files. Otherwise, we might encounter problems or even silent behavioural differences due to macros or defines not being defined as they should be. So in fact, our header and implementation files should make sure to always include "common.h" first. This commit does so by establishing a common include pattern. Header files inside of "src" will now always include "common.h" as its first other file, separated by a newline from all the other includes to make it stand out as special. There are two cases for the implementation files. If they do have a matching header file, they will always include this one first, leading to "common.h" being transitively included as first file. If they do not have a matching header file, they instead include "common.h" as first file themselves. This fixes the outlined problems and will become our standard practice for header and source files inside of the "src/" from now on. 
Next to including several files, our "common.h" header also declares
various macros which are then used throughout the project. As such, we
have to make sure to always include this file first in all
implementation files. Otherwise, we might encounter problems or even
silent behavioural differences due to macros or defines not being
defined as they should be. So in fact, our header and implementation
files should make sure to always include "common.h" first.

This commit does so by establishing a common include pattern. Header
files inside of "src" will now always include "common.h" as its first
other file, separated by a newline from all the other includes to make
it stand out as special. There are two cases for the implementation
files. If they do have a matching header file, they will always include
this one first, leading to "common.h" being transitively included as
first file. If they do not have a matching header file, they instead
include "common.h" as first file themselves.

This fixes the outlined problems and will become our standard practice
for header and source files inside of the "src/" from now on.
patch: `patch_diff` -> `patch_generated` 2016-05-26T18:01:08+00:00 Edward Thomson ethomson@microsoft.com 2015-11-24T20:19:59+00:00 8d44f8b78f7929c86b9e37acfe40fe707815bca6 






patch: abstract patches into diff'ed and parsed
2016-05-26T18:01:04+00:00

Edward Thomson
ethomson@edwardthomson.com

2015-09-11T12:37:12+00:00

804d5fe9f59f4d8548da9f650bc43050951f26d7

Patches can now come from a variety of sources - either internally
generated (from diffing two commits) or as the results of parsing
some external data.





Patches can now come from a variety of sources - either internally
generated (from diffing two commits) or as the results of parsing
some external data.







diff: don't feed large files to xdiff
2015-10-05T20:59:50+00:00

Edward Thomson
ethomson@microsoft.com

2015-09-29T16:18:17+00:00

6c014bcc54fb9923490f9af917dc43e3661e5782












Reorganize diff and add basic diff driver
2013-06-10T17:10:39+00:00

Russell Belfer
rb@github.com

2013-06-10T17:10:39+00:00

114f5a6c41ea03393e00ae41126a6ddb0ef39a15

This is a significant reorganization of the diff code to break it
into a set of more clearly distinct files and to document the new
organization.  Hopefully this will make the diff code easier to
understand and to extend.

This adds a new `git_diff_driver` object that looks of diff driver
information from the attributes and the config so that things like
function content in diff headers can be provided.  The full driver
spec is not implemented in the commit - this is focused on the
reorganization of the code and putting the driver hooks in place.

This also removes a few #includes from src/repository.h that were
overbroad, but as a result required extra #includes in a variety
of places since including src/repository.h no longer results in
pulling in the whole world.





This is a significant reorganization of the diff code to break it
into a set of more clearly distinct files and to document the new
organization.  Hopefully this will make the diff code easier to
understand and to extend.

This adds a new `git_diff_driver` object that looks of diff driver
information from the attributes and the config so that things like
function content in diff headers can be provided.  The full driver
spec is not implemented in the commit - this is focused on the
reorganization of the code and putting the driver hooks in place.

This also removes a few #includes from src/repository.h that were
overbroad, but as a result required extra #includes in a variety
of places since including src/repository.h no longer results in
pulling in the whole world.