Re: [ANNOUNCE] yap: Yet Another (Git) Porcelain

["Govind Salinas" <govind@sophiasuchtig.com>]

On Sat, Sep 6, 2008 at 2:01 PM, Jakub Narebski <jnareb@gmail.com> wrote:
> [Back on git mailing list]
>
> On Sat, 6 Sep 2008, Steven Walter wrote:
>> On Sat, Sep 6, 2008 at 11:36 AM, Jakub Narebski <jnareb@gmail.com> wrote:
>> >
>> > First, a question: how your yap porcelain differs from efforts of
>> > EasyGit (eg) and Pyrite?
>>
>> In the case of EasyGit, it differs in that yap's interface does not
>> have the requirement of being fully backwards-compatible with core
>> git.  Dropping that requirement gave me more freedom to simplify and
>> clean-up the interface.
>
> I can understand this.  EasyGit is more about making git self
> documenting than anything more, from what I understand.
>
>> To my knowledge, Pyrite does not support plugins.
>

Depends on what you mean by plugins.  There is a way to load what I call
extensions that you can use to add commands or modify the way existing
commands operate.  It is crude at the moment but it works.  I have a
proof of concept extension/plugin that adds different ways of specifying
revisions.  I assume you mean something similar.

> As far as I know Pyrite is one-man work.  Why not to join efforts,
> bringing those two projects together?  Both share the same language,
> Python.
>

Sadly, yes.  It is still just me.  I would welcome any help or additions.
I don't have as much time as I would like to work on it.  But as it stands I
have a web interface (no push/pull yet, I am waiting for the git http
push/pull to be done to make sure I have compatibility.

If you want to look at it, you can find it here...

http://gitorious.org/projects/pyrite


I am currently not doing much work on the command line interface since
people seemed to object to my ideas.  Instead I am focusing on the gui
instead.  Since you say you are not going to keep the command lines
compatible, what do you intend to do differently?

Good Luck.
Govind.