|
f05de9cb
|
2021-03-26T10:22:08
|
|
Update README.md for additional Delphi bindings
Delphi/Free pascal bindings targeting the latest version of libgit2
|
|
752dbecf
|
2021-03-04T09:45:12
|
|
README: it's actually our main branch
[skip ci]
|
|
82a091c4
|
2021-02-11T15:19:09
|
|
Add new bindings for the R language
|
|
|
4ac12634
|
2021-01-07T15:08:37
|
|
README: instructions for using libgit2 without compiling
|
|
|
21fe183e
|
2020-12-13T13:21:11
|
|
README: show v1.1 build status
|
|
|
8b29f66b
|
2020-11-24T00:01:32
|
|
ci: only report main branch in README status
|
|
|
f811cec9
|
2020-11-23T23:38:50
|
|
docs: update README with updated build links
|
|
4ad36338
|
2020-05-11T19:10:11
|
|
Update README.md
Add instructions for building libgit2 in MinGW environment
|
|
7a6c4122
|
2020-04-01T16:15:38
|
|
README.md: update build matrix to reflect our latest releases
|
|
|
87fc539f
|
2020-03-13T22:08:19
|
|
cmake: use install directories provided via GNUInstallDirs
We currently hand-code logic to configure where to install our artifacts
via the `LIB_INSTALL_DIR`, `INCLUDE_INSTALL_DIR` and `BIN_INSTALL_DIR`
variables. This is reinventing the wheel, as CMake already provide a way
to do that via `CMAKE_INSTALL_<DIR>` paths, e.g. `CMAKE_INSTALL_LIB`.
This requires users of libgit2 to know about the discrepancy and will
require special hacks for any build systems that handle these variables
in an automated way. One such example is Gentoo Linux, which sets up
these paths in both the cmake and cmake-utils eclass.
So let's stop doing that: the GNUInstallDirs module handles it in a
better way for us, especially so as the actual values are dependent on
CMAKE_INSTALL_PREFIX. This commit removes our own set of variables and
instead refers users to use the standard ones.
As a second benefit, this commit also fixes our pkgconfig generation to
use the GNUInstallDirs module. We had a bug there where we ignored the
CMAKE_INSTALL_PREFIX when configuring the libdir and includedir keys, so
if libdir was set to "lib64", then libdir would be an invalid path. With
GNUInstallDirs, we can now use `CMAKE_INSTALL_FULL_LIBDIR`, which
handles the prefix for us.
|
|
d91c6eda
|
2020-02-23T18:26:47
|
|
README: add language binding link to wasm-git
|
|
|
add54e6c
|
2020-02-19T11:31:01
|
|
README: update our build matrix to reflect current releases
As noted in docs/release.md, we only provide security updates for the
latest two releases. Let's thus drop the build status of both v0.27 and
v0.26 branches, adding the new v0.99 branch instead.
|
|
103a76b4
|
2020-01-30T17:58:43
|
|
Update link to Julia libgit2
|
|
e24b8852
|
2019-09-15T17:01:35
|
|
Update chat resources in README.md
|
|
84262643
|
2019-06-20T10:32:09
|
|
Fix broken link in README
|
|
|
62bbec5a
|
2019-05-24T11:09:51
|
|
SECURITY.md: split out security-relevant bits from readme
GitHub has recently introduced a new set of tools that aims to
ease the process around vulnerability reports and security fixes.
Part of those tools is a new security tab for projects that will
display contents from a new SECURITY.md file.
Move relevant parts from README.md to this new file to make use
of this feature.
|
|
1fd0903a
|
2019-03-05T18:47:45
|
|
Update URL to git2-rs
|
|
|
6f778351
|
2019-02-13T11:15:12
|
|
README: use correct badge for nightlies
The URL was incorrect for the nightly badge image; it was erroneously
showing the master branch continuous integration build badge.
|
|
|
f34faaa8
|
2019-02-12T16:45:57
|
|
README: include build badge for v0.28 builds
Include a build badge for `maint/v0.28` builds.
|
|
|
52a97eed
|
2019-01-28T12:16:50
|
|
ci: add coverity badge to the README
|
|
|
a74dd39b
|
2019-01-09T12:33:47
|
|
Use cdecl calling conventions on Win32
The recommendation from engineers within Microsoft is that libraries
should have a calling convention specified in the public API, and that
calling convention should be cdecl unless there are strong reasons to
use a different calling convention.
We previously offered end-users the choice between cdecl and stdcall
calling conventions. We did this for presumed wider compatibility: most
Windows applications will use cdecl, but C# and PInvoke default to
stdcall for WINAPI compatibility. (On Windows, the standard library
functions are are stdcall so PInvoke also defaults to stdcall.)
However, C# and PInvoke can easily call cdecl APIs by specifying an
annotation.
Thus, we will explicitly declare ourselves cdecl and remove the option
to build as stdcall.
|
|
|
3176d9b4
|
2018-09-22T19:58:37
|
|
README: add maint/v0.26 branch status
|
|
|
4b9a0880
|
2018-09-06T15:02:28
|
|
README: more CI status badges
|
|
|
e2613039
|
2018-09-18T13:52:08
|
|
README: rename "VSTS" to "Azure DevOps"
Visual Studio Team Services is now a family of applications named "Azure
DevOps". Update the README to refer to it thusly.
|
|
|
464305b7
|
2018-09-18T13:51:25
|
|
README: update the build badge to Azure Pipelines
VSTS is now a family of components; "Azure Pipelines" is the build and
release pipeline application.
|
|
|
76cfeb20
|
2018-09-03T19:27:30
|
|
README: remove travis
|
|
|
658b8e8a
|
2018-08-09T09:39:39
|
|
readme: remove appveyor build badge
|
|
|
a1ae41b8
|
2018-08-02T14:57:54
|
|
ci: add VSTS build badge to README
|
|
|
432dfda0
|
2018-03-22T09:32:28
|
|
README.md: detail how to list all build options
We do not list all build options inside of the README.md, and we
definitly shouldn't do so. But in order to help people discover what can
be configured, add instructions on how to have CMake generate the list
of all knobs together with their current value.
|
|
|
faf2629a
|
2018-03-22T09:27:18
|
|
README.md: fix link to `test_index_racy__diff`
The syntax for links is `[description](link)z, not the other way round.
Fix this.
|
|
|
68a3c0b1
|
2018-03-22T09:20:43
|
|
docs: reorganize documents
Our non-technical documents are currently floating around loosely in our
project's root, making it harden than necessary to discover what one is
searching for. We do have a "docs/" directory, though, which serves
exactly that purpose of hosting documentation.
Move our non-technical documentation into the "docs/" directory. Adjust
all links to these documents.
|
|
|
8f96cf9a
|
2018-03-22T09:13:18
|
|
README.md: add table of contents
By now, our README has grown quite long, and at multiple occassions
people were unable to find the correct spot in our documentation. Add a
table of contents to at least present an overview over all topics that
are being covered by our README.
|
|
|
699a48f8
|
2018-01-29T07:41:54
|
|
README.md: add notes on how to report security issues
|
|
|
5bcaba5d
|
2017-11-15T22:52:23
|
|
README: add up some marketing
|
|
|
8cbfa183
|
2017-11-15T22:42:35
|
|
README: document test output
|
|
|
c5d8682f
|
2017-11-12T14:47:11
|
|
README: clarify why one would run libgit2_clar
Since we recommend `ctest -V`, it's not clear why somebody would want to
run `libgit2_clar`. Indicate that it's helpful when running individual
tests or suites.
|
|
|
9e91a989
|
2017-11-12T13:05:59
|
|
README: provide quick start paragraph
Provide a very simple quick start paragraph that highlights how easy it
is to get started, and points people toward common problems.
|
|
|
dc985353
|
2017-11-12T12:03:21
|
|
README: drop VS command shell instructions
Users should not be advised to use the VS command prompt; instead, they
should let cmake find their Visual Studio installation.
|
|
|
b2d54cfa
|
2017-11-12T11:59:56
|
|
README: suggest `ctest -V` for getting started
Suggest that users run `ctest -V` instead of `make test` when getting
started. `ctest -V` is superior over alternatives as:
1. Unlike `make test`, it gives output. Users getting started with
the library believe that it is hung.
2. `ctest -V` shows verbose output; showing suite names is helpful for
giving users more feedback immediately.
|
|
b4e0d293
|
2017-09-09T09:54:58
|
|
README: Mention Guile-Git bindings.
|
|
|
1e27b89f
|
2017-05-11T13:56:55
|
|
Update README: VS -> VSTS
libgit2 is no longer used in Visual Studio Team Services, it's used in
Visual Studio Team Services.
|
|
|
19a04f67
|
2017-04-10T12:01:28
|
|
README: document our relation to changes in upstream
libgit2 is a mere consumer of changes which are trickling down from the
upstream git.git project. This commit documents the ramifications caused
by this relation.
|
|
5c06111b
|
2017-02-25T17:13:15
|
|
README: Mention how to run tests
|
|
329ce043
|
2016-12-20T12:14:22
|
|
Merge pull request #4037 from libgit2/cmn/goals
README: be more explicit in the goals and scope
|
|
87faeaec
|
2016-12-19T09:09:34
|
|
Gift deprecated in favor of SwiftGit2
|
|
8f064000
|
2016-12-19T13:54:55
|
|
README: be more explicit in the goals and scope
Make it clearer from the get-go that we do not aim to implement
user-facing commands from the git tool.
|
|
|
8044ee42
|
2016-08-29T09:38:20
|
|
README: adjust URL to libqgit2 repository
|
|
2976dcf8
|
2016-06-20T15:05:02
|
|
README: update "Getting Help" section
|
|
|
738ca6ee
|
2016-06-20T14:30:33
|
|
README: update bindings
Drop node-gitteh. Replace outdated PowerShell bindings with PSGit.
|
|
|
0820d0c8
|
2016-06-20T14:24:17
|
|
README: improve contributing paragraph
|
|
|
69d11971
|
2016-06-20T14:16:50
|
|
README: disambiguate what to distribute source of
Indicate that if you make changes to libgit2 that you must distribute
the source _to libgit2_, not the source _of your program_.
|
|
|
1f8cb02f
|
2016-02-25T14:51:00
|
|
CONVENTIONS: update to include general public API principles
|
|
|
a066b4cb
|
2015-12-26T18:31:22
|
|
Merge pull request #3552 from ReadmeCritic/master
Update README URLs based on HTTP redirects
|
|
1ce509fe
|
2015-12-26T15:51:32
|
|
Update libgit2-glib link
|
|
22829b74
|
2015-12-23T21:27:40
|
|
Fixed minor typo in README.md.
|
|
|
1181ca0c
|
2015-12-17T08:36:04
|
|
Update README URLs based on HTTP redirects
|
|
37c84dc5
|
2015-07-05T10:07:48
|
|
Increase required version of cmake to 2.8
|
|
69560cc0
|
2015-05-28T15:19:53
|
|
Changed README to use new OCaml bindings to git
|
|
e702dc2e
|
2015-05-14T15:49:51
|
|
Updated dlibgit link.
|
|
57aa839c
|
2015-05-04T09:41:34
|
|
Android build doesn't need deps/regex
deps/regex was included in Android build because Android NDK 4 has
a packaging bug and doesn't have the regular expression functions defined
in its libc.so. The bug has been fixed in subsequent Android NDK releases.
If it is still necessary to work around the bug in Android NDK 4, we
should consider to use an option like ANDROID_NDK_RELEASE or
ANDROID_NDK_RELEASE_NUM.
|
|
ecf1c3c3
|
2015-02-23T11:18:52
|
|
README: provide some more explanation about TLS
|
|
35425b51
|
2015-02-04T01:06:07
|
|
README.md: Add Swift bindings "Gift"
|
|
|
7cfbf3b7
|
2015-01-15T16:56:58
|
|
README: Point to libgit2 account's AppVeyor badge
Microsoft is sponsoring a Pro account at AppVeyor for the libgit2
and LibGit2Sharp projects. Point to that account's badge.
|
|
c5c8ece1
|
2015-01-14T02:14:38
|
|
Use svg instead of png to get better image quality
|
|
|
ed09e044
|
2014-12-14T16:18:09
|
|
Mention the init function in the README
This fixes #2731.
|
|
a7e06cb0
|
2014-12-10T10:11:37
|
|
readme: Add AppVeyor build status badge/link
|
|
|
037b2a8b
|
2014-12-10T09:55:29
|
|
readme: Make Travis build status badge reflect the state of master
|
|
|
775d831b
|
2014-12-10T10:03:07
|
|
readme: Trim trailing lines
|
|
|
15bea02c
|
2014-10-31T11:24:02
|
|
docs: explicitly document the threading caveats
Talk about sharing objects and error messages; but the most important
part is about what to do with the cryptographic libraries, which sadly
have to become to responsibility of the application.
|
|
|
79b0ae4e
|
2014-10-27T10:30:57
|
|
Flip THREADSAFE's default to ON
Threads are here to stay; and for a while now, users have had to call
the initialization function which sets up threads and crypto regardless
of whether the library was built threadsafe or not.
|
|
18925129
|
2014-10-06T16:17:01
|
|
Fix README.md
|
|
a2a23322
|
2014-09-30T04:16:17
|
|
the wiki, it is dead
|
|
2c22193b
|
2014-09-16T08:56:33
|
|
Fix typo
|
|
b4913705
|
2014-09-15T12:11:48
|
|
Add Rust to the language bindings list
|
|
d747ec18
|
2014-08-25T20:50:06
|
|
add Julia to the language bindings list
|
|
2ef20da0
|
2014-07-13T17:52:33
|
|
Updated perl bindings link
|
|
562516ec
|
2014-05-13T22:43:59
|
|
Add R bindings to the README
|
|
486bc366
|
2014-02-26T16:37:08
|
|
Add project list and update readme
|
|
|
68a19ca9
|
2014-02-20T11:26:51
|
|
Clarify C compatibility policy
and a couple of other minor doc fixups.
|
|
c85d606e
|
2014-01-16T11:36:06
|
|
Merge pull request #2044 from libgit2/coverity
Run Coverity scan on Travis
|
|
|
4ef9a508
|
2014-01-15T13:58:11
|
|
Update README to include Java, PowerShell bindings
|
|
|
4caf0df0
|
2014-01-13T15:43:29
|
|
Add coverity scan badge to readme
|
|
7b50c784
|
2013-12-27T15:15:48
|
|
docs: Remove non existing wrapper from the readme
libgit2net stopped to exist, all hail libgit2sharp
|
|
|
dcfdb977
|
2013-11-01T10:51:12
|
|
Relicense examples under CC0
|
|
63d1fad4
|
2013-10-24T15:30:31
|
|
fix typos in README.md
|
|
|
2baee9f8
|
2013-10-23T13:17:51
|
|
README: add a note about the optional dependencies
|
|
caf93341
|
2013-10-17T16:01:43
|
|
slightly clarified the "license" portion of `README.md" + formatting all over
fixed typo `can can` -> `can`
|
|
|
e5e2710b
|
2013-10-17T01:52:20
|
|
slightly clarified the "license" portion of `README.md" + formatting all over
added the second change suggested by @nulltoken (with two extra words :) )
|
|
|
20b5d300
|
2013-10-17T00:28:08
|
|
slightly clarified the "license" portion of `README.md" + formatting all over
There are commercial open source applications, hence proprietary seems to be a better term.
Also:
- Trimmed header `=`'s to match text length
- made libgit2 stand out everywhere
- pretty printing links
- irc link for those with the correct setup
|
|
01cd5ae3
|
2013-09-01T19:43:35
|
|
Add instructions about buiding for Android to README.md
|
|
|
f2cda906
|
2013-08-31T17:42:38
|
|
Point to the right Go bindings
|
|
a402179a
|
2013-08-31T09:25:25
|
|
Update readme to point to the currently maintained Erlang bindings. Namely: https://github.com/carlosmn/geef
|
|
|
bef59b1b
|
2013-07-19T12:56:47
|
|
Update README.md
|
|
|
41a93cc6
|
2013-07-19T12:43:08
|
|
Clarify when to use github issues
Suggest that github issues are to be used for bug reports, while questions about usage should be directed to StackOverflow.
|
|
3e3d332b
|
2013-07-19T18:04:11
|
|
Tidy up the methods of contacting the project
Updated the methods of getting involved with the project and asking
questions.
|
|
|
743048f1
|
2013-04-19T10:29:50
|
|
Fix some minor issues
|
|
1cfaaa9e
|
2013-04-17T13:48:26
|
|
Update link to Perl bindings
|
|
7d5b0f8b
|
2013-04-09T09:28:40
|
|
Updated link to Haskell bindings
The old one hasn't been updated in a long time. This one is current.
|
|
4f1da3a2
|
2013-02-06T16:55:09
|
|
removed obsolete reference to api.html
|
|
a8182d49
|
2013-01-30T12:24:38
|
|
Let people know that the ML is deprecated
|