From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: pasky@ucw.cz, git@vger.kernel.org
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Cogito-0.8 (former git-pasky, big changes!)
Date: Tue, 26 Apr 2005 14:22:45 +1000 [thread overview]
Message-ID: <1114489365.7111.40.camel@gaston> (raw)
In-Reply-To: <20050426032422.GQ13467@pasky.ji.cz>
On Tue, 2005-04-26 at 05:24 +0200, Petr Baudis wrote:
> Hello,
>
> here goes Cogito-0.8, my SCMish layer over Linus Torvald's git tree
> history tracker. This package was formerly called git-pasky, however
> this release brings big changes. The usage is significantly different,
> as well as some basic concepts; the history changed again (hopefully the
> last time?) because of fixing dates of some old commits. The .git/
> directory layout changed too.
>
> .../...
Unless you already did this in the latest release, it would be nice to
have something like havign all the low level tools be by default in some
~/lib/git or whatever, and only the cg-* scripts in ~/bin on install,
unless maybe you pass some kind of I_AM_A_REAL_GIT=1 on the make
line ...
I don't really plan to use the low level tools, and I don't like the way
they clobber my bin namespace :)
Ben.
next prev parent reply other threads:[~2005-04-26 4:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 3:24 [ANNOUNCE] Cogito-0.8 (former git-pasky, big changes!) Petr Baudis
2005-04-26 3:29 ` Petr Baudis
2005-04-26 4:12 ` Mike Taht
2005-04-26 12:23 ` Petr Baudis
2005-04-26 17:40 ` Paul Jackson
2005-04-26 15:15 ` Martin Atukunda
2005-04-26 4:22 ` Benjamin Herrenschmidt [this message]
2005-04-26 4:58 ` Jeff Garzik
2005-04-26 5:18 ` Daniel Barkalow
2005-04-26 5:40 ` Al Viro
2005-04-26 6:03 ` [PATCH] Don't use commit-id in building Daniel Barkalow
2005-04-26 7:02 ` [ANNOUNCE] Cogito-0.8 (former git-pasky, big changes!) Philip Pokorny
2005-04-26 20:43 ` Petr Baudis
2005-04-26 13:36 ` Morten Welinder
2005-04-26 22:21 ` Pavel Machek
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=1114489365.7111.40.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pasky@ucw.cz \
/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.