github.com/mono/libgit2sharp.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2015-02-21	Teach UpdateLibgit2ToSha.ps1 to copy native binaries on windows only	nulltoken

2014-11-04	Update libgit2 to 3f8d005	Edward Thomson
	https://github.com/libgit2/libgit2/compare/e0383fa...3f8d005
2014-10-14	Update libgit2 to build with GIT_TRACE	Edward Thomson
	Build libgit2 with tracing information so that we can provide it to consumers.
2014-09-19	Use a build properties file instead of custom build actions to copy native ↵	Sam Harwell
	binaries
2014-05-28	[UpdateLibGit2] Add v12 csproj format to description.	Marius Ungureanu

2013-11-04	Fix UpdateLibgit2ToSha.ps1 path context handling	nulltoken

2013-07-18	Remove ".dll" extension from dll-name declaration	Ben Straub

2013-07-18	Ensure libgit2 always uses STDCALL convention	Ben Straub

2013-07-11	Teach UpdateLibgit2ToSha.ps1 to take arbitrary libgit2 library name.	Jameson Miller

2013-07-11	Update libgit2 binaries to bd67979	nulltoken
	https://github.com/libgit2/libgit2/compare/9d9fff3...bd67979
2013-06-09	Ensure built binaries names match with resources	nulltoken

2013-05-26	Update libgit2 binaries to 5aee963	Ben Straub
	https://github.com/libgit2/libgit2/compare/b641c00...5aee963 This also change naming convention of libgit2 binaries. Each LibGit2Sharp version works against a specific version of libgit2. LibGit2Sharp managed code relies on the dynamic loader to find the proper libgit2 binary. This binary is located in a directory structure next to the managed assembly, and the loader is instructed to search within this directory structure. Up until now, the binary being searched for was bearing a generic name: [lib]git2.(dll\|so\|dylib). However, on Windows, if one older version of the native binary, with the same name, is already loaded in the memory, the loader will reuse this one, no matter what directory it's been loaded from. Chances are great that this old libgit2 version is incompatible with what the newer version of LibGit2Sharp expects from its API or behavior. In order to mitigate this, libgit2 binaries are now suffixed with the libgit2 commit sha they've been build from and LibGit2Sharp will bind to a specifically named binary: - git2-{short_sha}.dll on Windows - libgit2-{short_sha}.so on Linux - libgit2-{short_sha}.dylib on Mac OS X. This should allow one to run two different future version of LibGit2Sharp, side by side, without any name clash.
2012-12-23	Add script to update libgit2	Ben Straub
	A call to ".\UpdateLibgit2ToSha.ps1 deadbeef" will: - Fetch libgit2 - Checkout the sha, if it exists as a commit - Build 32- and 64-bit variants of the library, and copy them to NativeBinaries - Update the libgit2_sha.txt file