Git development
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@ucw.cz>
To: git@vger.kernel.org
Subject: [ANNOUNCE] Cogito-0.10
Date: Mon, 9 May 2005 01:34:31 +0200	[thread overview]
Message-ID: <20050508233431.GP9495@pasky.ji.cz> (raw)

  Hello,

  I'm happy to announce new release of Cogito, my SCM-like layer upon
the Linus' GIT tree history storage engine, aiming for user-friendliness.
Get it at

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

or cg-update if you already have any decently fresh version.

  The highlights are cg-logging of individual files, cg-export
foo.tar.gz, fixed cg-init of fresh trees (it makes an initial commit
now), cg-commit message processing enhancements (in cooperation mainly
with Marcel Holtmann), cg-restore, cg-admin-uncommit, and cg-X* stuff in
a library directory. And also merge with Linus, which brings some stuff
chronologically pre-cogito-0.9, but I forgot to pull before release.

  Usage changes:
    * cg-update without parameters now does not recover lost files;
      that functionality was moved to cg-restore which can do that
      with individual files only too.
    * cg-update and cg-pull w/o arguments default to "origin" again.
      Everyone rejoices.
    * cg-init SOURCE_LOC is now deprecated, cg-init should not be
      called directly for the cloning stuff anymore. Use it only for
      creating new repositories now.
    * cg-clone can take a -s argument now which makes it to clone to
      the current directory instead of a subdirectory.

  I think the usage is very stabilized by now, and is actually quite
unlikely to change anymore - you can safely start to get used to it. The
only change still queued is removing cg-init SOURCE_LOC functionality
altogether; I'm delaying that yet mainly because of the
http://www.kernel.org/git/ text. ;-)

  I think we are overall stabilizing very nicely, and might actually
be nearing cogito-1.0 (but let that not stop you doing anything yet...
perhaps except rewriting the whole thing in Befunge).

  Please note that my patch queue is basically empty now. The only
things I have marked for consideration yet are:

4778 N   Apr 22 Morten Welinder ( 7.0K) [PATCH] Constify
5607 N T Apr 28 Philip Pokorny  ( 2.5K) PATCH[*/4]: Allow tree-id to return the ID of a tree object

  So if you have a patch you think I should have in my tree too, please
resend it. Do not forget to put the patch inline to the mail body or as
a text/plain attachment, and to sign it off.

  Have fun,

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor

             reply	other threads:[~2005-05-08 23:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-08 23:34 Petr Baudis [this message]
2005-05-09  4:47 ` [ANNOUNCE] Cogito-0.10 H. Peter Anvin

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=20050508233431.GP9495@pasky.ji.cz \
    --to=pasky@ucw.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