Git development
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] Cogito-0.16.2
Date: Thu, 15 Dec 2005 00:10:19 +0100	[thread overview]
Message-ID: <20051214231019.GK22159@pasky.or.cz> (raw)

  Hello,

  this is Cogito version 0.16.2, 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/

  Very few changes since the last release - one testcase, trivial fix,
documentation improvements. And one important bugfix! If you are a
cg-clean user, certainly upgrade - cg-clean in 0.16.1 had a serious bug
which would cause it remove all subdirectories when running from the
source root with the -d option - which is rather nasty if you have any
uncommitted local changes there.

  Now we finally have a testcase for cg-clean, and the cg-clean code was
further tweaked to reduce potential for any more code mistakes. The
major reason for both 0.16.1 and 0.16.2 were cg-clean bugs, but
hopefully no more problems are waiting for us in this realm, and the
rest of Cogito seems to be thankfully pretty stable throughout the 0.16
line, so I expect things to finally calm down a bit here.

  I spent the last two hours making a large patch fixing all potentially
whitespace-unsafe Cogito code, but I've decided to keep it for 0.17 only
- Cogito meeting with whitespaces is a very rare occasion, and such
a large patch is bound to contain some new bugs coming from trivial
mistakes and such.

  Also, Cogito is now very ineffective when cloning big-packed
repositories over the git protocol or over ssh, since git-fetch-pack
unpacks the objects on the local side, which bogs things down a lot and
makes the repository grow into enormous proportions - I'm not yet sure
if I will backport the fix to 0.16 since I want to be maximally careful
not to gravely break anything again and keep 0.16 as stable as possible.
(Hm. Call this "the Debian dilemma". ;-)

  The new stuff since 0.16.1 is:

Pavel Roskin:
      cg-clean test
      cg-clean: be safer by running everything from relpath

Petr Baudis:
      cg-clean testcase: Minor tidyup
      cg-clean testcase: Clarify description
      Fixed cg-clean removing ALL subdirs when invoked from root
            (Discovered and originally fixed by Pavel Roskin.)
      Fix cg-status reporting every merge as a squash-merge
      Improve cg-admin-setuprepo documentation
      In the cg-commit text, give the user hint on how to abort
      cogito-0.16.2

  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.

             reply	other threads:[~2005-12-14 23:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-14 23:10 Petr Baudis [this message]
2005-12-15  6:57 ` [ANNOUNCE] Cogito-0.16.2 Alan Chandler
2005-12-15  8:56   ` Petr Baudis

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=20051214231019.GK22159@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox