From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: [ANNOUNCE] CGIT v0.11.2 Released
Date: Fri, 13 Mar 2015 16:27:21 +0100 [thread overview]
Message-ID: <CAHmME9rJyQyZGjJwKajq1or-PNO4Uosr6Nsjxxbq3NyWAQ89Bg@mail.gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi folks,
CGit 0.11.2 is now available, with numerous bug fixes.
== CGit on the Web ==
* homepage: http://git.zx2c4.com/cgit/about/
* git repository: http://git.zx2c4.com/cgit/
* git clone: git://git.zx2c4.com/cgit
* mailing list: cgit at lists.zx2c4.com
* mailing list subscribe: http://lists.zx2c4.com/mailman/listinfo/cgit
== ChangeLog v0.11.2 ==
22 files changed, 444 insertions(+), 92 deletions(-)
Additions:
* New sample filter: filters/gentoo-ldap-authentication.lua
This filter shows how you might use lualdap for real authentication.
Changes:
* Uses internally Git 2.3.2
* No longer display blank links for submodules when there's no way of
resolving the submodule location.
Bug fixes:
* Numerous code quality fixes from sparse
* Take into account leading slashes when comptuing links
* Set up environment variables before making clone urls
== Downloading ==
* http://git.zx2c4.com/cgit/snapshot/cgit-0.11.2.tar.xz
sha256:
2e126e770693d7296c7eb5eb83b809410aef29870bfe8f54da072a3f4d813e3b
* For verification git tag v0.11.2 is signed with my public key:
zx2c4.com/keys/AB9942E6D4A4CFC3412620A749FC7012A5DE03AE.asc
Thanks to everyone who contributed to this release!
Jason Donenfeld
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIbBAEBCAAGBQJVAwHVAAoJEEn8cBKl3gOucJUP+Pb4RHICgKRFKUsLiShVcN/T
tlv97VWfTJ/KukDJIfWe20Wgb6PdDrOxVjzexbDXdg5bnJIti8PKuTzHvmoFyUnH
PMQUESvFWHm0sUy22VGzpi45BrUi/79J9ioxqbrZne4l5Yz+AlE26Rj7BYeFqlGN
JFQmTBeDk4K0LLdf7YiO281oWWDz33AQRY2TpWtD0fpdo3tHOjbHVBT4Pf1p1cZ3
kEVVk/VEpitgV+wzEgiDfhj5E02guYeWJwZcABUruzPozAlpkxqCr2W0AqcLD+hy
va3YtntvYjI/c6PkUFoUCvOwmjqqOaWq2uZFqf3IqWEuHsDOKTqV0F9to0ed4vnj
HulF3EdEORk3ST4EHeJpN1WDsGLWByCsMC3ChvtNVspWEa14kqnDsdHu99AVqajQ
VFxftJyLIVWQ+WlaITZygLR+qWtqIU7w6Zhk7u4SQi79ZX6q4WIthzSJJhIJVPSM
BWml+SrooLp1JVm6RNNgSCTgpG20pbAGGgLlSLJAbZtDBpMmvr+tKe8I92sai3aE
AebSc9JeplVgEJn+nh74SAe6l5yIR+/z1rTogQ4zJkvN4AI9WrzET4OzmadIemg4
jq0yoKAQiRqHOOk1jOtHQZGIdWsatBn4jj7U8f05GhFhuBTpw1OpQiQVSjKN+cLV
bf0YzylhVgfGASw60FE=
=nhxe
-----END PGP SIGNATURE-----
reply other threads:[~2015-03-13 15:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHmME9rJyQyZGjJwKajq1or-PNO4Uosr6Nsjxxbq3NyWAQ89Bg@mail.gmail.com \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).