Git development
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: git@vger.kernel.org
Subject: [ANNOUNCE] Cogito-0.16rc1
Date: Fri, 11 Nov 2005 21:24:24 +0100	[thread overview]
Message-ID: <20051111202424.GW30496@pasky.or.cz> (raw)

  Hello,

  I'm announcing the release of Cogito version 0.16rc1, the human-friendly
version control UI for Linus' GIT tool. Share and enjoy at:

	http://www.kernel.org/pub/software/scm/cogito/

  Tons of new features are balanced by other tons of bugfixes, but since
there was a lot of stuff, I would like to give it a while to stabilize,
so that 0.16 itself is really stable. Therefore, I will run this through
the rc process. (Note that 0.16rc1 was tagged the last night, and few
more stuff already landed into git since then, but nothing critical.)

  I'm not sure if many people will actually use the rc releases (I guess
they are either following stable releases or the latest version from
git), but at least it's an anchor point for me - from now on, I will
keep a stable branch in parallel with the development branch (or rather,
I will fork out the development branch when I'm about to do any major
change), so the bugfixes will get back to the latest stable version,
and I won't feel that bad about not releasing for so long.

  The notable new stuff includes:

  * Significant fetching surgery:
    - host:path location now means git+ssh instead of rsync (but it
      is deprecated in favour of explicit protocol name - safer and
      less confusing for you)
    - git+ssh uses packed transport instead of the dated git-ssh-fetch
    - Tags fetching is now much more reliable, saner and faster
    - More robust rsync fetching (for anyone actually still using it)
    - Speedup of the whole thing (the progressbar was actually slowing
      the process down so much that I'm almost afraid to say it)
  * The one-file merging autoresolver covers much more cases now;
    it still probably doesn't handle file-symlink and file-directory
    conflicts (actually, I didn't even test anything related to that
    yet), but otherwise it should handle pretty much any conflict now
    (except that it yet won't make sure that you resolved the conflict
    before committing)
  * New command cg-admin-setuprepo for creating public repositories
  * Major cg-restore surgery - more pleasant to use, more powerful,
    more robust

  * cg-push -t will push tags
  * cg-merge -j will join projects with disjoint histories
  * cg-merge --squash will do the "squash merge" (see docs for details)
  * cg-log --summary will show the shortlog output
  * cg-diff -s will show diffstat
  * cg-reset --adds-removes will reset only index (cancel the
    adds/removes recorded, from the user perspective)
  * cg-status DIRNAME will show the status relative to that directory
  * cg-status -s will filter for only the given status flags
  * cg-tag always creates the tag object
  * First draft of the VCS-neutral interface implemented as
    contrib/neutral.sh

  * Speedups all around (e.g. per-file cg-log SIXTY times)
  * Reorganized cg-help output
  * More new tests in the testsuite
  * Documentation stuff - the "scripted tutorial", README expanded,
    tiny stuff all around

  * Heaps of both major and minor bugfixes; I won't name them, you can
    look at "cg-log -s -r cogito-0.15.1.." - but you should definitely
    upgrade, at last when the stable 0.16 comes out


P.S.: See us at #git @ FreeNode!

  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-11-11 20:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20051111202424.GW30496@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=git@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