From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: git@vger.kernel.org, Andreas Ericsson <ae@op5.se>
Subject: Re: [cogito-0.18.2] Documentation/Code Mismatch: cg-switch -l
Date: 27 May 2008 10:48:29 +0200 [thread overview]
Message-ID: <m3mymc2kv6.fsf@localhost.localdomain> (raw)
In-Reply-To: 20080527080417.GA32209@lifebook.rekudos.net
Mark Lawrence <nomad@null.net> writes:
>> On Mon May 26, 2008 at 02:19:04PM +0200, Andreas Ericsson wrote:
>>> Mark Lawrence wrote:
>>>>
>>>>I don't know if this is a bug or just my understanding, but I'm having
>>>>trouble matching the behaviour of "cg-switch -l" with the documentation.
>>>
>>> Cogito became officially unmaintained a very long time ago (late 2006?)
>>> and will almost certainly not work properly with any half-recent version
>>> of git. Don't use it.
>>
>> Oh. That's only <sarcasm>slightly annoying</sarcasm> to learn now, given
>> that I've spent the past two years learning and converting my projects
>> over to cogito :/ Could somebody *please* update the cogito web page at
>> http://git.or.cz/cogito/ and put a big (maybe even blinking) notice
>> informing people of this?
Git Homepage (http://git.or.cz/) states:
Cogito
Cogito was a popular version control system on top of Git, aiming
at seamless user interface and ease of use. It provided much
better user interface in the past but later improvements of Git
made it mostly obsolete and it is not maintained anymore. Please
migrate to Git itself.
I guess that it should be mentioned stronly also on Cogito homepage,
although the date of latest release ([2006-10-19]) is a bit of hint...
BTW. maintaner (Petr Baudis <pasky@suse.cz>) welcomes patches; the
repository is at http://repo.or.cz/r/git-homepage.git
>> Bit of a shame that it's died though, because I appreciated the simpler
>> interface (and some of the output I find nicer).
BTW. I think one of the reasons Cogito died was that it tried to hide
index, and used single branch per repository paradigm when dealing
with remote repositories while git acquired powerful tool (git-remote)
to deal with multi-branches remote repositories... and
author/maintainer didn't have time to modify Cogito to include those
features.
I'd say that Cogito was one of forces behind making Git easier to use
(for example git-filter-branch is the equivalent of cg-admin-rewrite-hist,
a single thing that was possible in Cogito but was not possible in Git,
created when Cogito was announced to be no longer maintained/abandoned).
>> On a more practical note, am I likely to suffer any issues using pure
>> git on repos created with cogito?
I don't thinks so.
> And a related question: is there any kind of cogito replacement that
> provides a simplified interface? As far as versioning tools go, git is
> quite low-level...
There are two projects aiming at easier git experience: EasyGit (which
is mainly documentation improvement) and Pyrite (which will include
GUI), but IIRC both are in early stages of development.
P.S. As Cogito is OSS project, you can always [try to] revive it,
I think even without changing its name...
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-05-27 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 8:04 [cogito-0.18.2] Documentation/Code Mismatch: cg-switch -l Mark Lawrence
2008-05-27 8:11 ` Wincent Colaiuta
2008-05-27 8:33 ` Ittay Dror
2008-05-27 8:48 ` Jakub Narebski [this message]
2008-05-29 17:28 ` Petr Baudis
2008-05-29 22:17 ` fmt, was " Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2008-05-26 11:18 Mark Lawrence
2008-05-26 12:19 ` Andreas Ericsson
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=m3mymc2kv6.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=ae@op5.se \
--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;
as well as URLs for NNTP newsgroup(s).