mirror of
https://github.com/AGWA/git-crypt.git
synced 2025-12-05 20:40:05 -08:00
Prepare 0.6.0 release
This commit is contained in:
13
NEWS
13
NEWS
@@ -1,3 +1,16 @@
|
||||
v0.6.0 (2017-11-26)
|
||||
* Add support for OpenSSL 1.1 (still works with OpenSSL 1.0).
|
||||
* Switch to C++11 (gcc 4.9 or higher now required to build).
|
||||
* Allow GPG to fail on some keys (makes unlock work better if there are
|
||||
multiple keys that can unlock the repo but only some are available).
|
||||
* Allow the repo state directory to be configured with the
|
||||
git-crypt.repoStateDir git config option.
|
||||
* Respect the gpg.program git config option.
|
||||
* Don't hard code path to git-crypt in .git/config on Linux (ensures
|
||||
repo continues to work if git-crypt is moved).
|
||||
* Ensure git-crypt's gpg files won't be treated as text by Git.
|
||||
* Minor improvements to build system, documentation.
|
||||
|
||||
v0.5.0 (2015-05-30)
|
||||
* Drastically speed up lock/unlock when used with Git 1.8.5 or newer.
|
||||
* Add git-crypt(1) man page (pass ENABLE_MAN=yes to make to build).
|
||||
|
||||
13
NEWS.md
13
NEWS.md
@@ -1,6 +1,19 @@
|
||||
News
|
||||
====
|
||||
|
||||
######v0.6.0 (2017-11-26)
|
||||
* Add support for OpenSSL 1.1 (still works with OpenSSL 1.0).
|
||||
* Switch to C++11 (gcc 4.9 or higher now required to build).
|
||||
* Allow GPG to fail on some keys (makes unlock work better if there are
|
||||
multiple keys that can unlock the repo but only some are available).
|
||||
* Allow the repo state directory to be configured with the
|
||||
git-crypt.repoStateDir git config option.
|
||||
* Respect the gpg.program git config option.
|
||||
* Don't hard code path to git-crypt in .git/config on Linux (ensures
|
||||
repo continues to work if git-crypt is moved).
|
||||
* Ensure git-crypt's gpg files won't be treated as text by Git.
|
||||
* Minor improvements to build system, documentation.
|
||||
|
||||
######v0.5.0 (2015-05-30)
|
||||
* Drastically speed up lock/unlock when used with Git 1.8.5 or newer.
|
||||
* Add git-crypt(1) man page (pass `ENABLE_MAN=yes` to make to build).
|
||||
|
||||
2
README
2
README
@@ -69,7 +69,7 @@ encryption and decryption happen transparently.
|
||||
|
||||
CURRENT STATUS
|
||||
|
||||
The latest version of git-crypt is 0.5.0, released on 2015-05-30.
|
||||
The latest version of git-crypt is 0.6.0, released on 2017-11-26.
|
||||
git-crypt aims to be bug-free and reliable, meaning it shouldn't
|
||||
crash, malfunction, or expose your confidential data. However,
|
||||
it has not yet reached maturity, meaning it is not as documented,
|
||||
|
||||
@@ -70,8 +70,8 @@ encryption and decryption happen transparently.
|
||||
Current Status
|
||||
--------------
|
||||
|
||||
The latest version of git-crypt is [0.5.0](NEWS.md), released on
|
||||
2015-05-30. git-crypt aims to be bug-free and reliable, meaning it
|
||||
The latest version of git-crypt is [0.6.0](NEWS.md), released on
|
||||
2017-11-26. git-crypt aims to be bug-free and reliable, meaning it
|
||||
shouldn't crash, malfunction, or expose your confidential data.
|
||||
However, it has not yet reached maturity, meaning it is not as
|
||||
documented, featureful, or easy-to-use as it should be. Additionally,
|
||||
|
||||
@@ -31,7 +31,7 @@
|
||||
#ifndef GIT_CRYPT_GIT_CRYPT_HPP
|
||||
#define GIT_CRYPT_GIT_CRYPT_HPP
|
||||
|
||||
#define VERSION "0.5.0"
|
||||
#define VERSION "0.6.0"
|
||||
|
||||
extern const char* argv0; // initialized in main() to argv[0]
|
||||
|
||||
|
||||
@@ -7,8 +7,8 @@
|
||||
-->
|
||||
<refentryinfo>
|
||||
<title>git-crypt</title>
|
||||
<date>2015-05-30</date>
|
||||
<productname>git-crypt 0.5.0</productname>
|
||||
<date>2017-11-26</date>
|
||||
<productname>git-crypt 0.6.0</productname>
|
||||
|
||||
<author>
|
||||
<othername>Andrew Ayer</othername>
|
||||
|
||||
Reference in New Issue
Block a user