From: Petr Baudis <pasky@suse.cz>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] Cogito-0.16.1
Date: Mon, 12 Dec 2005 02:12:10 +0100 [thread overview]
Message-ID: <20051212011210.GC12373@pasky.or.cz> (raw)
Hello,
this is Cogito version 0.16.1, the next stable release of the
human-friendly version control UI for the Linus' GIT tool. Share
and enjoy at:
http://www.kernel.org/pub/software/scm/cogito/
This crispy new release gives you a few minor to medium bugfixes and
a significant cg-patch speedup. You can reach it as the "v0.16" branch
of the Cogito repository. Note that this is just the stable branch, more
interesting stuff is happenning (and especially going to happen) on the
master development branch; if everything goes well, I might release
cogito-0.17rc1 at the end of this week).
So the new stuff since 0.16 is:
Jonas Fonseca:
cg-merge: Improve the hook description
cg-status: handle subdirs when listing heads
Petr Baudis:
Fix cg-admin-setuprepo warning on missing post-update hook
Initial cg-push to a remote branch wouldn't work properly
Fix cg-object-id <singleletter>
Fix unsafe sed usage in scripts
cg-clean -n will just pretend to remove stuff
Make cg-clean whitespace-safe
If you use filenames with spaces _and_ cg-clean (or cg-clean
at all, after all), you should certainly upgrade!
bash-3.1-related fixes
Fix broken cg-log FILE in subdirectory
Drastically speed up cg-patch
cogito-0.16.1
Happy hacking,
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
next reply other threads:[~2005-12-12 1:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 1:12 Petr Baudis [this message]
2005-12-12 1:14 ` [ANNOUNCE] Cogito-0.16.1 Petr Baudis
2005-12-12 3:03 ` Don Koch
2005-12-13 1:02 ` Problems with cg-admin-setuprepo Paul Dickson
2005-12-13 1:16 ` Petr Baudis
2005-12-13 1:26 ` [ANNOUNCE] Cogito-0.16.1 Paul Dickson
2005-12-13 16:56 ` Petr Baudis
2005-12-13 18:02 ` Paul Dickson
2005-12-13 22:31 ` Petr Baudis
2005-12-14 1:40 ` Paul Dickson
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=20051212011210.GC12373@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.