From: Abhijit Bhopatkar <bain@devslashzero.com>
To: Jan Hudec <bulb@ucw.cz>
Cc: Frank Li <lznuaa@gmail.com>, Pieter de Bie <pieter@frim.nl>,
git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>,
Jonas Fonseca <fonseca@diku.dk>,
Marco Costalba <mcostalba@gmail.com>,
David Aguilar <davvid@gmail.com>,
Henk <henk_westhuis@hotmail.com>,
tortoisegit-dev <tortoisegit-dev@googlegroups.com>
Subject: Re: [RFC] Common library for Git GUIs
Date: Wed, 18 Feb 2009 11:32:04 +0530 [thread overview]
Message-ID: <2fcfa6df0902172202n70c355dbg2a3f8ef50b9ea65c@mail.gmail.com> (raw)
In-Reply-To: <20090218055700.GE2216@efreet.light.src>
>> I think TortoiseGit need C\C++ git library, which should be also used
>> by git itself. Otherwise, it is difficult sync with git.
>
> I don't mean to reimplement a single bit of what is implemented in git
> itself. I want to factor out some stuff that is above git, only useful for
> _graphical_ user interfaces.
>
Ah!!
Sorry i missed that detail in the orig long mail :(
I still don't think it making things simpler. What you are proposing
is yet one more abstraction. But me thinks cli abstraction is enough.
Abstractions at interface levels are usefull, abstractions at
functional level (gui's vs clis) are complex and don't solv anything.
BAIN
next prev parent reply other threads:[~2009-02-18 6:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 21:24 [RFC] Common library for Git GUIs Jan Hudec
2009-02-17 12:55 ` Guilhem Bonnefille
2009-02-17 20:39 ` Jan Hudec
[not found] ` <e5bfff550902162337m43156398kb06320796838c953@mail.gmail.com>
2009-02-17 7:40 ` Fwd: " Marco Costalba
2009-02-17 19:28 ` Jan Hudec
2009-02-18 8:04 ` Marco Costalba
2009-02-19 7:30 ` David Aguilar
2009-02-17 20:08 ` Pieter de Bie
2009-02-17 21:21 ` Jan Hudec
2009-02-17 23:45 ` Johannes Schindelin
2009-02-18 5:52 ` Jan Hudec
2009-02-18 1:38 ` Frank Li
2009-02-18 5:57 ` Jan Hudec
2009-02-18 6:02 ` Abhijit Bhopatkar [this message]
2009-02-18 5:56 ` Abhijit Bhopatkar
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=2fcfa6df0902172202n70c355dbg2a3f8ef50b9ea65c@mail.gmail.com \
--to=bain@devslashzero.com \
--cc=bulb@ucw.cz \
--cc=davvid@gmail.com \
--cc=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=henk_westhuis@hotmail.com \
--cc=lznuaa@gmail.com \
--cc=mcostalba@gmail.com \
--cc=pieter@frim.nl \
--cc=spearce@spearce.org \
--cc=tortoisegit-dev@googlegroups.com \
/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).