From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: [ANNOUNCE] CGIT v1.1 Released
Date: Wed, 23 Nov 2016 05:39:27 +0100 [thread overview]
Message-ID: <CAHmME9o_19=ia2zFgcGSqcYCyJpHSVDK15QEk-Ma7-Kq6QQQ_w@mail.gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi folks,
CGit 1.1 is now available. This is mainly a bug fix and stability release, but
there are a few nice new features this release too. This release cycle has
also seen an improvement in contribution workflow. Several cgit core
developers now share the task of integrating user contributions, which we hope
will decrease submit-to-review-to-merge latency.
== CGit on the Web ==
* homepage: https://git.zx2c4.com/cgit/about/
* git repository: https://git.zx2c4.com/cgit/
* git clone: git://git.zx2c4.com/cgit
* mailing list: cgit at lists.zx2c4.com
* mailing list subscribe: https://lists.zx2c4.com/mailman/listinfo/cgit
== ChangeLog v1.1 ==
30 files changed, 389 insertions(+), 319 deletions(-)
Notable Changes:
* Single-child trees are now elided into single links. Instead of having to
click through depths of links, now a single link will to to the maximum
point of depth.
* Continuing our commitment to supporting kernel.org, we've adopted some of
their style changes in our CSS, now allowing for colored even/odd table rows
with a nice hover effect.
* Snapshot name prettification is now consistent, so that the 'v' prefix
stripping only occurs when it won't create any collisions. This is a slight
change of behavior, but I imagine cases of folks relying on the old broken
behavior are few and far between.
* We now use Git 2.10.2 internally, which has brought with it numerous
cleanups and a gradual shift away from 20 byte uchar arrays and toward the
newer "object_id" structure.
== Downloading ==
* https://git.zx2c4.com/cgit/snapshot/cgit-1.1.tar.xz sha256:
0889af29be15fc981481caa09579f982b9740fe9fd2860ab87dff286f4635890
* For verification git tag v1.1 is signed with my public key:
zx2c4.com/keys/AB9942E6D4A4CFC3412620A749FC7012A5DE03AE.asc
Thanks to everyone who contributed to this release!
Jason Donenfeld
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAlg1HTsACgkQSfxwEqXe
A65/eA//Y0b2rVaPvwFuUbf3QEI2lm9yxgf5P2yzHGrbaHxeUjpzU57rpw39Xg6w
6SGwiu6ulSinVbz4deUUhvIfW8O9HoSGGnzLokePNosmIDyFreiHZUkp0looFspU
n22jLdcMgTt2ZsV0U6sReCD4fsrprs3pwlGQVUapshDP5laLo9xPiWNREMF7fJzi
BxFzsCO2jVM9L19tNVXkfJzSo+h/RqUD8lXh2HY0t8vCp44+23Mipx/rLgveWA8l
gpT0P5kcyFbD6j1WVZOUDaQG5BEGoPpZlCc8XaAdv574dznSfkTV2iO3JvqVtJn6
pJr1PXZVPsYY9n0NKmPPmj/Nv42ZhrfRnvfXpMPHRFyM890rHy7fksi2MhYo8hkK
ztKbcRx8zdI9mpcrZP3+ECgWY0AmgywWdeGYq5/3uBpPLhqXKCGNqh0+sraDC+/H
zk07Epl3cOsHXCphqJu9XSBNkr8XHSpZi/ifpK6aVtoz7GVK9+qnmH9lWUAvuzsq
w7sSj5R+onLsrn3X8RDkyp/rnIA9Duf+MpvHS6xqeYInjvBB4bwdhVfN4Ns+cYjf
6/u4r0+mlDyLn24gXzELUNW3wy4R7QgWcw5ZX0ItGKooOlRkYOmgrMyeeBNwaMs+
0BIA91TAsWpNIWUs0Dyhj/BnoEO5vf8iO+nE2CFpOAuats+Pj00=
=Dmc4
-----END PGP SIGNATURE-----
next reply other threads:[~2016-11-23 4:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 4:39 Jason [this message]
2016-11-24 19:01 ` john
2016-11-24 20:28 ` Jason
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='CAHmME9o_19=ia2zFgcGSqcYCyJpHSVDK15QEk-Ma7-Kq6QQQ_w@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).