From: larsh-K3XMUd79hPisTnJN9+BGXg@public.gmane.org
To: cgit-K3XMUd79hPisTnJN9+BGXg@public.gmane.org
Cc: git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [ANNOUNCE] CGIT 0.9.0.1
Date: Mon, 13 Jun 2011 12:49:54 +0000 [thread overview]
Message-ID: <20110613124954.GA737@hjemli.net> (raw)
A bugfix release of cgit (a web interface to git repositories) is now
available from http://hjemli.net/git/cgit.
Shortlog since v0.9
===================
Ferry Huberts (2):
source_filter: fix a memory leak
new_filter: correctly initialise all arguments for a new filter
Jamie Couture (1):
scan-tree.c: avoid memory leak
Jonathon Mah (1):
Fix escaping of paths with spaces
Julius Plenz (2):
fix two encoding bugs
Add advice about scan-path in cgitrc.5.txt
Lars Hjemli (9):
cgitrc.5: tar.xz is a supported snapshot format
tests/setup.sh: add support for known bugs
tests: add tests for links with space in path and/or args
shared.c: do not modify const memory
ui-repolist.c: do not return random/stale data from read_agefile
ui-snapshot.c: remove debug cruft
ui-log.c: do not link from age column
ui-plain.c: fix html and links generated by print_dir() and print_dir_entry()
CGIT 0.9.0.1
Lukas Fleischer (5):
Remove unused variable from cgit_diff_tree().
Fix memory leak in http_parse_querystring().
Avoid null pointer dereference in reencode().
Avoid null pointer dereference in cgit_print_diff().
Properly escape ampersands inside HTML attributes
Mark Lodato (1):
fix virtual-root if script-name is ""
Stefan Gehn (1):
Fix crash when projectsfile cannot be opened
next reply other threads:[~2011-06-13 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 12:49 larsh-K3XMUd79hPisTnJN9+BGXg [this message]
2011-06-13 13:49 ` [ANNOUNCE] CGIT 0.9.0.1 Todd Zullinger
2011-06-13 14:42 ` Lars Hjemli
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=20110613124954.GA737@hjemli.net \
--to=larsh-k3xmud79hpistnjn9+bgxg@public.gmane.org \
--cc=cgit-K3XMUd79hPisTnJN9+BGXg@public.gmane.org \
--cc=git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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).