Date: Mon, 12 Dec 2005 02:12:10 +0100
From: Petr Baudis <pasky@suse.cz>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] Cogito-0.16.1
Message-ID: <20051212011210.GC12373@pasky.or.cz>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.11
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1691
Lines: 47

  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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/