From: Guilhem Bonnefille <guilhem.bonnefille@gmail.com>
To: "André Harms" <andre.harms@kuhlsolutions.de>
Cc: git@vger.kernel.org
Subject: Re: Modern Git GUI
Date: Tue, 26 Jan 2010 23:39:25 +0100 [thread overview]
Message-ID: <8b65902a1001261439l309325dap43d0196e6e163f4f@mail.gmail.com> (raw)
In-Reply-To: <e39c1dcf1001231340p67448584pfdbc453cc8fb9ca7@mail.gmail.com>
Hi,
IMHO, a really important question is: why do we have so many
started-not-terminated GUIs?
My point of view:
- a "good" GUI is a GUI that integrates well with a desktop
- a "good" GUI is a GUI that reuse an already existing/known metaphor
The most difficult is that raw Git is "stupid content tracker". So, a
complete GUI will expose too many features to end-user:
- which workflow: pull, push, email, ssh, ...
- topic branches: rebasing or merging
- and what about higher level feature: stash, stg, top git...
So, reading this, possible good GUIs are plugins for IDE with smallest
Git support.
2010/1/23 André Harms <andre.harms@kuhlsolutions.de>:
> Is there anybody who agrees or disagrees? I really would appreciate
> some feedback about that idea.
--
Guilhem BONNEFILLE
-=- JID: guyou@im.apinc.org MSN: guilhem_bonnefille@hotmail.com
-=- mailto:guilhem.bonnefille@gmail.com
-=- http://nathguil.free.fr/
next prev parent reply other threads:[~2010-01-26 22:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 21:40 Modern Git GUI André Harms
2010-01-24 9:50 ` Matthieu Moy
2010-01-24 20:43 ` André Harms
2010-01-25 14:25 ` Johannes Schindelin
2010-01-25 14:30 ` John Tapsell
2010-01-26 11:35 ` Michael J Gruber
2010-01-26 22:39 ` Guilhem Bonnefille [this message]
2010-01-28 15:11 ` Maxime Lévesque
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=8b65902a1001261439l309325dap43d0196e6e163f4f@mail.gmail.com \
--to=guilhem.bonnefille@gmail.com \
--cc=andre.harms@kuhlsolutions.de \
--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).